Skip to content

[release-4.20] OCPBUGS-62167: Fix - NetworkManager restart or crash renders br-ex unusable #5353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 5 commits into
base: release-4.20
Choose a base branch
from
Open

[release-4.20] OCPBUGS-62167: Fix - NetworkManager restart or crash renders br-ex unusable #5353

wants to merge 5 commits into from
+5 −1

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #5304

/assign openshift-ci-robot

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Oct 15, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-54682 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.20] OCPBUGS-62167: Fix - NetworkManager restart or crash renders br-ex unusable

In response to this:

This is an automated cherry-pick of #5304

/assign openshift-ci-robot

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 [release-4.20] OCPBUGS-54682: Fix - NetworkManager restart or crash renders br-ex unusable [release-4.20] OCPBUGS-62167: Fix - NetworkManager restart or crash renders br-ex unusable Oct 15, 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 15, 2025
@openshift-ci-robot
Copy link
Contributor

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

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 #5304

/assign openshift-ci-robot

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.

@sdodson
Copy link
Member

sdodson commented Oct 16, 2025

/label backport-risk-assessed approved staff-eng-approved

@mkowalski
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 16, 2025
@sdodson
Copy link
Member

sdodson commented Oct 20, 2025

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sdodson: This pull request references Jira Issue OCPBUGS-62167, 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.

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

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.

@sdodson
Copy link
Member

sdodson commented Oct 20, 2025

/label backport-risk-assessed approved

@sdodson sdodson added 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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 21, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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:

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

@sdodson
Copy link
Member

sdodson commented Oct 21, 2025

/verified @mkowalski

@openshift-ci-robot
Copy link
Contributor

@sdodson: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified @mkowalski

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.

@sdodson
Copy link
Member

sdodson commented Oct 21, 2025

/verified by @mkowalski

@sdodson
Copy link
Member

sdodson commented Oct 21, 2025

/label staff-eng-approved

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

@sdodson: This PR has been marked as verified by @mkowalski.

In response to this:

/verified by @mkowalski

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 added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 21, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f587a1b and 2 for PR HEAD f1f8d6f in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 04d7cb3 and 1 for PR HEAD f1f8d6f in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 22, 2025

@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/bootstrap-unit f1f8d6f link false /test bootstrap-unit
ci/prow/e2e-gcp-op-1of2 f1f8d6f link unknown /test e2e-gcp-op-1of2
ci/prow/e2e-gcp-op-single-node f1f8d6f link unknown /test e2e-gcp-op-single-node
ci/prow/images f1f8d6f link unknown /test images
ci/prow/e2e-aws-ovn-upgrade f1f8d6f link unknown /test e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-op-2of2 f1f8d6f link unknown /test e2e-gcp-op-2of2
ci/prow/e2e-aws-ovn f1f8d6f link unknown /test e2e-aws-ovn

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pablintino pablintino Awaiting requested review from pablintino

@RishabhSaini RishabhSaini Awaiting requested review from RishabhSaini

Assignees

@rbbratta rbbratta

@mkowalski mkowalski

@eurijon eurijon

@openshift-ci-robot openshift-ci-robot

@lyman9966 lyman9966

@anuragthehatter anuragthehatter

@imatza-rh imatza-rh

@rioliu-rh rioliu-rh

@mhanss mhanss

@ptalgulk01 ptalgulk01

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.