Skip to content

OCPBUGS-115900: CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides - #3124

Open
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-2998-to-release-5.0
Open

OCPBUGS-115900: CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides#3124
openshift-cherrypick-robot wants to merge 1 commit into
openshift:release-5.0from
openshift-cherrypick-robot:cherry-pick-2998-to-release-5.0

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #2998

/assign cgoncalves

Teach the ovnkube node startup wrapper to source OVN_ENCAP_IP from the
per-node env-overrides ConfigMap and pass it to ovnkube as --encap-ip.
Normalize whitespace in the override so single-IP and comma-separated
encap IP values are passed safely as one shell argument, and keep
coverage for the optional env-overrides mount used for day2 updates.

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot

openshift-ci-robot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CORENET-7330

Details

In response to this:

This is an automated cherry-pick of #2998

/assign cgoncalves

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 1eb1267e-3a88-4148-bb4f-a1765cedbbd8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@cgoncalves

Copy link
Copy Markdown

/cherry-pick release-4.22

@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@cgoncalves: once the present PR merges, I will cherry-pick it on top of release-4.22 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.22

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cgoncalves

Copy link
Copy Markdown

/test images

@tssurya

tssurya commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-ovn-upgrade-ipsec

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn-fdp-qe
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-windows
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6-ipsec
/test e2e-ovn-ipsec-step-registry
/test hypershift-e2e-aks

@cgoncalves

Copy link
Copy Markdown

CNO secondary encap CI lanes being added in openshift/release#83663

@cgoncalves

Copy link
Copy Markdown

/retest-required

@openshift-ci openshift-ci Bot changed the title [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides [CNF-26697](https://redhat.atlassian.net/browse/CNF-26697): [release-5.0] [CORENET-7330](https://redhat.atlassian.net/browse/CORENET-7330): Allow per-node OVN encap IP override via env-overrides Aug 21, 2026
@cgoncalves

cgoncalves commented Aug 21, 2026

Copy link
Copy Markdown

/retitle CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides

@openshift-ci openshift-ci Bot changed the title [CNF-26697](https://redhat.atlassian.net/browse/CNF-26697): [release-5.0] [CORENET-7330](https://redhat.atlassian.net/browse/CORENET-7330): Allow per-node OVN encap IP override via env-overrides CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides Aug 21, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 21, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references CNF-26697 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

This is an automated cherry-pick of #2998

/assign cgoncalves

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@cgoncalves

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

@cgoncalves: This pull request references CNF-26697 which is a valid jira issue.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tssurya

tssurya commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

/test

@tssurya

tssurya commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

/test e2e-metal-ipi-ovn-secondary-encap

1 similar comment
@andreaskaris

Copy link
Copy Markdown
Contributor

/test e2e-metal-ipi-ovn-secondary-encap

@andreaskaris

Copy link
Copy Markdown
Contributor

@andreaskaris

Copy link
Copy Markdown
Contributor

/test e2e-metal-ipi-ovn-secondary-encap

@SchSeba

SchSeba commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Hi @cgoncalves @andreaskaris Thanks for covering on this one.
the lane is green :)

@tssurya can you please review and add the lgtm/approve labels?

/retest-required

@tssurya tssurya left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, tssurya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2026
@SchSeba

SchSeba commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

/retest-required

@SchSeba

SchSeba commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed
/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

@SchSeba: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-release-oversight, openshift-staff-engineers, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed
/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@SchSeba

SchSeba commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

/retest-required

2 similar comments
@SchSeba

SchSeba commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

/retest-required

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/retest-required

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Hi @tssurya, this two lanes continue to failed but they are not related to this change at all.

can you override I feeling we are just wasting CI resources on this..

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/jira cherrypick OCPBUGS-115895

@openshift-ci-robot

openshift-ci-robot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

@SchSeba: Jira Issue OCPBUGS-115895 has been cloned as Jira Issue OCPBUGS-115900. Will retitle bug to link to clone.
/retitle OCPBUGS-115900: CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides

Details

In response to this:

/jira cherrypick OCPBUGS-115895

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot changed the title CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides OCPBUGS-115900: CNF-26697: [release-5.0] CORENET-7330: Allow per-node OVN encap IP override via env-overrides Sep 2, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 2, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-115900, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-115895 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #2998

/assign cgoncalves

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/jire refresh

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/retest-required

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-115900, which is invalid:

  • expected dependent Jira Issue OCPBUGS-115895 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-115900, which is invalid:

  • expected dependent Jira Issue OCPBUGS-115895 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is Closed (Done) instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@SchSeba

SchSeba commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 2, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-115900, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-115895 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-115895 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (core-networking-bot@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@tssurya

tssurya commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants