[release-4.20] OCPBUGS-62602: configure-ovs: work around a Cisco switch issue #5321

openshift-cherrypick-robot · 2025-10-01T06:24:16Z

This is an automated cherry-pick of #5274

/assign cybertron

/cherrypick release-4.19 release-4.18

When a slave is detached from a bond (e.g. during NetworkManager reactivation) before LACP negotiation completes, some Cisco switches mishandle LACP packets with agg=0, and disable the port. To work around this, if a bond slave is UP and LACP is enabled, wait up to 5 seconds for both ends to reach the "collecting,distributing" state before reattaching the interface. If negotiation does not complete within this window, a warning is logged but configuration continues. Note: This is a switch error, and sending agg=00 is valid. This is a workaround that only hides the issue on affected hardware and may reduce system's fault tolerance. Signed-off-by: Xin Long <[email protected]>

openshift-ci-robot · 2025-10-01T06:24:27Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60805 has been cloned as Jira Issue OCPBUGS-62602. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-62602: configure-ovs: work around a Cisco switch issue

In response to this:

This is an automated cherry-pick of #5274

/assign cybertron

/cherrypick release-4.19 release-4.18

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 · 2025-10-01T06:24:50Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-62602, 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-60805 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.

In response to this:

This is an automated cherry-pick of #5274

/assign cybertron

/cherrypick release-4.19 release-4.18

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.

pablintino · 2025-10-01T11:17:14Z

/verified by testing in Cisco environment with the content of main (4.21)
/lgtm
Clean cherry-pick that should work independently of the MCO release version.

openshift-ci-robot · 2025-10-01T11:17:27Z

@pablintino: This PR has been marked as verified by testing in Cisco environment with the content of main (4.21).

In response to this:

/verified by testing in Cisco environment with the content of main (4.21)
/lgtm
Clean cherry-pick that should work independently of the MCO release version.

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 · 2025-10-01T11:17:44Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [pablintino]

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

cybertron · 2025-10-01T16:06:49Z

/jira refresh
/label backport-risk-assessed

openshift-ci-robot · 2025-10-01T16:06:54Z

@cybertron: This pull request references Jira Issue OCPBUGS-62602, 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-60805 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.

In response to this:

/jira refresh
/label backport-risk-assessed

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.

cybertron · 2025-10-01T16:08:15Z

/jira refresh

openshift-ci-robot · 2025-10-01T16:08:24Z

@cybertron: This pull request references Jira Issue OCPBUGS-62602, 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-60805 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-60805 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 @rbbratta

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.

knobunc · 2025-10-01T18:38:54Z

/label staff-eng-approved

openshift-ci · 2025-10-01T19:35:58Z

@openshift-cherrypick-robot: 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/e2e-gcp-mco-disruptive	`9120a52`	link	false	`/test e2e-gcp-mco-disruptive`
ci/prow/bootstrap-unit	`9120a52`	link	false	`/test bootstrap-unit`
ci/prow/e2e-azure-ovn-upgrade-out-of-change	`9120a52`	link	false	`/test e2e-azure-ovn-upgrade-out-of-change`
ci/prow/e2e-aws-mco-disruptive	`9120a52`	link	false	`/test e2e-aws-mco-disruptive`
ci/prow/e2e-gcp-op-ocl	`9120a52`	link	false	`/test e2e-gcp-op-ocl`

Full PR test history. Your PR dashboard.

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.

openshift-ci-robot · 2025-10-01T19:41:13Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-62602
✔️ 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-62602 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

This is an automated cherry-pick of #5274

/assign cybertron

/cherrypick release-4.19 release-4.18

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-cherrypick-robot · 2025-10-01T19:42:08Z

@openshift-cherrypick-robot: new pull request created: #5323

In response to this:

This is an automated cherry-pick of #5274

/assign cybertron

/cherrypick release-4.19 release-4.18

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-robot · 2025-10-02T23:01:23Z

Fix included in accepted release 4.20.0-0.nightly-2025-10-02-162542

openshift-cherrypick-robot assigned cybertron Oct 1, 2025

openshift-cherrypick-robot mentioned this pull request Oct 1, 2025

OCPBUGS-60805: configure-ovs: work around a Cisco switch issue #5274

Merged

openshift-ci bot changed the title ~~[release-4.20] OCPBUGS-60805: configure-ovs: work around a Cisco switch issue~~ [release-4.20] OCPBUGS-62602: configure-ovs: work around a Cisco switch issue Oct 1, 2025

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. labels Oct 1, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 1, 2025

openshift-ci bot requested review from isabella-janssen and pablintino October 1, 2025 06:24

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 1, 2025

openshift-ci bot assigned pablintino Oct 1, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 1, 2025

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 1, 2025

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 1, 2025

openshift-ci bot assigned anuragthehatter, eurijon, imatza-rh, lyman9966, mhanss, ptalgulk01, rbbratta and rioliu-rh Oct 1, 2025

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 1, 2025

openshift-ci bot requested a review from rbbratta October 1, 2025 16:08

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 1, 2025

openshift-merge-bot bot merged commit d707114 into openshift:release-4.20 Oct 1, 2025
17 of 22 checks passed

openshift-cherrypick-robot mentioned this pull request Oct 1, 2025

[release-4.19] OCPBUGS-62649: configure-ovs: work around a Cisco switch issue #5323

Merged

[release-4.20] OCPBUGS-62602: configure-ovs: work around a Cisco switch issue #5321

[release-4.20] OCPBUGS-62602: configure-ovs: work around a Cisco switch issue #5321

Uh oh!

Conversation

openshift-cherrypick-robot commented Oct 1, 2025

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

pablintino commented Oct 1, 2025

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

openshift-ci bot commented Oct 1, 2025

Uh oh!

cybertron commented Oct 1, 2025

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

cybertron commented Oct 1, 2025

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

knobunc commented Oct 1, 2025

Uh oh!

openshift-ci bot commented Oct 1, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Oct 1, 2025

Uh oh!

openshift-cherrypick-robot commented Oct 1, 2025

Uh oh!

openshift-merge-robot commented Oct 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

15 participants