Skip to content

Comments

OCPBUGS-62913: Configure sec nic EIPv6 address with NODAD and maximum lifetime#2797

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
jcaamano:ocpbugs-56783-4.20
Oct 16, 2025
Merged

OCPBUGS-62913: Configure sec nic EIPv6 address with NODAD and maximum lifetime#2797
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
jcaamano:ocpbugs-56783-4.20

Conversation

@jcaamano
Copy link
Contributor

@jcaamano jcaamano commented Oct 9, 2025

Aligning it to what we do for primary nic EIPv6 addresses. NODAD is required since it is possible for an EIPv6 to be configured in two nodes at the same time during a short failover time window.

(cherry picked from commit b828680)

Aligning it to what we do for primary nic EIPv6 addresses. NODAD is
required since it is possible for an EIPv6 to be configured in two nodes
at the same time during a short failover time window.

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
(cherry picked from commit b828680)
@jcaamano
Copy link
Contributor Author

jcaamano commented Oct 9, 2025

/jira cherrypick OCPBUGS-60468

@openshift-ci-robot
Copy link
Contributor

@jcaamano: Jira Issue OCPBUGS-60468 has been cloned as Jira Issue OCPBUGS-62913. Will retitle bug to link to clone.
/retitle OCPBUGS-62913: Configure sec nic EIPv6 address with NODAD and maximum lifetime

Details

In response to this:

/jira cherrypick OCPBUGS-60468

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 Configure sec nic EIPv6 address with NODAD and maximum lifetime OCPBUGS-62913: Configure sec nic EIPv6 address with NODAD and maximum lifetime Oct 9, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 9, 2025
@openshift-ci-robot
Copy link
Contributor

@jcaamano: This pull request references Jira Issue OCPBUGS-62913, 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-60468 to target a version in 4.21.0, but it targets "4.21" 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:

Aligning it to what we do for primary nic EIPv6 addresses. NODAD is required since it is possible for an EIPv6 to be configured in two nodes at the same time during a short failover time window.

(cherry picked from commit b828680)

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 requested review from kyrtapz and tssurya October 9, 2025 15:39
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 9, 2025
@jcaamano
Copy link
Contributor Author

jcaamano commented Oct 9, 2025

/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 Oct 9, 2025
@openshift-ci-robot
Copy link
Contributor

@jcaamano: This pull request references Jira Issue OCPBUGS-62913, 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.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-60468 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-60468 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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 requested a review from anuragthehatter October 9, 2025 16:07
Copy link
Contributor

@tssurya tssurya left a comment

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 Oct 9, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, 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

@tssurya
Copy link
Contributor

tssurya commented Oct 10, 2025

/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 Oct 10, 2025
@jcaamano
Copy link
Contributor Author

/retest
/override ci/prow/lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 10, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint

Details

In response to this:

/retest
/override ci/prow/lint

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.

@sdodson
Copy link
Member

sdodson commented Oct 11, 2025

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 11, 2025
@jcaamano
Copy link
Contributor Author

/retest-required
/override ci/prow/lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint

Details

In response to this:

/retest-required
/override ci/prow/lint

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.

@jcaamano
Copy link
Contributor Author

/override ci/prow/lint

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 14, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/lint

Details

In response to this:

/override ci/prow/lint

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.

@huiran0826
Copy link
Contributor

/verified by pre-merge testing

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 15, 2025
@openshift-ci-robot
Copy link
Contributor

@huiran0826: This PR has been marked as verified by pre-merge testing.

Details

In response to this:

/verified by pre-merge testing

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
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 84cdb99 and 2 for PR HEAD 0e9f3c7 in total

@sdodson
Copy link
Member

sdodson commented Oct 15, 2025

/label staff-eng-approved

@jcaamano
Copy link
Contributor Author

/retest-required

2 similar comments
@sdodson
Copy link
Member

sdodson commented Oct 16, 2025

/retest-required

@jcaamano
Copy link
Contributor Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2025

@jcaamano: 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 0e9f3c7 link false /test security
ci/prow/okd-scos-e2e-aws-ovn 0e9f3c7 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw 0e9f3c7 link unknown /test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
ci/prow/e2e-aws-ovn-windows 0e9f3c7 link unknown /test e2e-aws-ovn-windows
ci/prow/e2e-gcp-ovn 0e9f3c7 link unknown /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.

@jcaamano
Copy link
Contributor Author

/override ci/prow/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

The job has passed before on this same commit. All the test cases pass, the job timeouts on later stages. We are tracking this as a known issue being addressed here

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2025

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

Details

In response to this:

/override ci/prow/4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade

The job has passed before on this same commit. All the test cases pass, the job timeouts on later stages. We are tracking this as a known issue being addressed here

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 050ed2c into openshift:release-4.20 Oct 16, 2025
28 of 30 checks passed
@openshift-ci-robot
Copy link
Contributor

@jcaamano: Jira Issue Verification Checks: Jira Issue OCPBUGS-62913
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-62913 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Aligning it to what we do for primary nic EIPv6 addresses. NODAD is required since it is possible for an EIPv6 to be configured in two nodes at the same time during a short failover time window.

(cherry picked from commit b828680)

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-robot
Copy link
Contributor

Fix included in accepted release 4.20.0-0.nightly-2025-10-18-160952

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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.