Skip to content

[release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides - #3148

Open
SchSeba wants to merge 1 commit into
openshift:release-4.22from
SchSeba:encap-ip-from-file-and-env-4.22
Open

SchSeba wants to merge 1 commit into
openshift:release-4.22from
SchSeba:encap-ip-from-file-and-env-4.22

Conversation

@SchSeba

@SchSeba SchSeba commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

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.

Manual cherry-pick because #3147 failed.
Had to drop DpuNodeLeaseRenewInterval and DpuNodeLeaseDuration from the
env-overrides DaemonSet test, bootstrap fields do not exist on
the release-4.22 OVNConfigBoostrapResult API.

@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

@coderabbitai

coderabbitai Bot commented Sep 3, 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 94ff5fa1-5f20-4252-90de-f0aaed3be27d

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.

@SchSeba

SchSeba commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

/retitle [release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides- #3148

@openshift-ci openshift-ci Bot changed the title Allow per-node OVN encap IP override via env-overrides [release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides- #3148 Sep 3, 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 Sep 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

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

  • expected dependent Jira Issue OCPBUGS-115900 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:

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.

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-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 3, 2026
@SchSeba

SchSeba commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

the security failing is not related to my changes..

@SchSeba

SchSeba commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

/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 7, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-119956, 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 (4.22.0) matches configured target version for branch (4.22.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-115900 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-115900 targets the "5.0.0" version, which is one of the valid target versions: 5.0.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.

@SchSeba

SchSeba commented Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

/retitle [release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides

@openshift-ci openshift-ci Bot changed the title [release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides- #3148 [release-4.22] OCPBUGS-119956: Allow per-node OVN encap IP override via env-overrides Sep 8, 2026
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.

Drop DpuNodeLeaseRenewInterval and DpuNodeLeaseDuration from the
env-overrides DaemonSet test; those bootstrap fields do not exist on
the release-4.22 OVNConfigBoostrapResult API.

(cherry picked from commit 0ac3f7e)
Signed-off-by: Sebastian Sch <sebassch@gmail.com>
@SchSeba
SchSeba force-pushed the encap-ip-from-file-and-env-4.22 branch from d6037d0 to 773e6e3 Compare September 8, 2026 08:13
@tssurya

tssurya commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

waiting on https://redhat-internal.slack.com/archives/CDCP2LA9L/p1788854122124259?thread_ts=1778514163.567789&cid=CDCP2LA9L and https://redhat-internal.slack.com/archives/CDCP2LA9L/p1788854142187619?thread_ts=1778514163.567789&cid=CDCP2LA9L

all information on a specific PR's backport should be on the PR, (eg any conflicts? why wasn't cherry-pick bot used, any new code changes etc, and mostly importantly use -x to cherry-pick from merged commit on newer branches) -same ask goes for 4.21 and 4.20 PRs and all backport PRs really

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-119956, 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 (4.22.0) matches configured target version for branch (4.22.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-115900 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-115900 targets the "5.0.0" version, which is one of the valid target versions: 5.0.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.

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

Details

In response to this:

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.

Manual cherry-pick because #3147 failed.
Had to drop DpuNodeLeaseRenewInterval and DpuNodeLeaseDuration from the
env-overrides DaemonSet test, bootstrap fields do not exist on
the release-4.22 OVNConfigBoostrapResult API.

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 Sep 8, 2026

Copy link
Copy Markdown
Contributor

QA for this bug and the bugs on newer release can't be the bot - please change it to an engineer from Telco side who did the +1 reviews for you

@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-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2026
@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 4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade
/test 4.22-upgrade-from-stable-4.21-e2e-azure-ovn-upgrade
/test 4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade
/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

@openshift-ci

openshift-ci Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SchSeba, 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 Sep 8, 2026
@tssurya

tssurya commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

will add risk assessed post CI results

@SchSeba

SchSeba commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@SchSeba

SchSeba commented Sep 9, 2026

Copy link
Copy Markdown
Contributor Author

/retest

2 similar comments
@SchSeba

SchSeba commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@SchSeba

SchSeba commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@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 14, 2026
@SchSeba

SchSeba commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@danwinship

Copy link
Copy Markdown
Contributor

@SchSeba needs someone to confirm the fix and set /verified

@SchSeba

SchSeba commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

Hi @danwinship, thanks for the comment! we have a lane to confirm it's working as checked by @tssurya already in #3148 (comment) so I think we can mark it as verified by ci no?

@SchSeba

SchSeba commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@tssurya

tssurya commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

@SchSeba : yea that's why the bug has QA assignee who sets the label once all required verifications are done they should add the verified on the PRs

@SchSeba

SchSeba commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@SchSeba

SchSeba commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

@elhadjici can you please add the label for the QE here?

@elhadjici

Copy link
Copy Markdown

/verified by @elhadjici

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

Copy link
Copy Markdown
Contributor

@elhadjici: This PR has been marked as verified by @elhadjici.

Details

In response to this:

/verified by @elhadjici

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-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD fe422f7 and 2 for PR HEAD 773e6e3 in total

@SchSeba

SchSeba commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 6d4ef08 and 1 for PR HEAD 773e6e3 in total

@SchSeba

SchSeba commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@SchSeba

SchSeba commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@SchSeba

SchSeba commented Sep 16, 2026

Copy link
Copy Markdown
Contributor Author

Hi @tssurya @danwinship will it be possible to override the e2e-gcp-ovn one it's failing on un related stuff about this change and it feels a bit of waste of resources continue the /retest

@tssurya

tssurya commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

/verified by @elhadjici

please add details around how you verified this when you add the label for others to know

@tssurya

tssurya commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Hi @tssurya @danwinship will it be possible to override the e2e-gcp-ovn one it's failing on un related stuff about this change and it feels a bit of waste of resources continue the /retest

the rule for override is simple - find the TRT bug or general bug for the test failing in the gcp lane and link it here and I can override it.
clearly it has to be something failing all over across PRs - so there must be a bug logged already against the team whose tests are failing - so use sippy or other component readiness dashboard tools to get the OCPBUGS link to find the relevant bug and drop a comment that analyses the CI failure along with the bug

@openshift-ci

openshift-ci Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

@SchSeba: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 773e6e3 link false /test security
ci/prow/e2e-gcp-ovn 773e6e3 link true /test e2e-gcp-ovn

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.

@elhadjici

Copy link
Copy Markdown

/verified by @elhadjici

please add details around how you verified this when you add the label for others to know

Ok thanks for the feedback.

After applying the changes, to verify, run the command below on any node and verify that the IP addresses are updated to match the new ones defined in the ConfigMap.
sudo ovs-vsctl show

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.

5 participants