Skip to content

OCPBUGS-63650: configure-ovs: copy lldp mode to br-ex port#5698

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rbbratta:OCPBUGS-63650-lldp-enable
May 14, 2026
Merged

OCPBUGS-63650: configure-ovs: copy lldp mode to br-ex port#5698
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rbbratta:OCPBUGS-63650-lldp-enable

Conversation

@rbbratta
Copy link
Copy Markdown
Contributor

copy connection.lldp to ovs-if-phys0 connection, so we can enable LLDP RX using NetworkManager.

copy connection.lldp to ovs-if-phys0 connection, so we can
enable LLDP RX using NetworkManager.
@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 Feb 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rbbratta: This pull request references Jira Issue OCPBUGS-63650, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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:

copy connection.lldp to ovs-if-phys0 connection, so we can enable LLDP RX using NetworkManager.

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.

@mkowalski
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@cybertron
Copy link
Copy Markdown
Member

/jira refresh
/assign @RishabhSaini
/verified by @rbbratta

Ross tested this on a real baremetal cluster, so we're confident it will do what we need.

@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 Feb 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

3 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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rbbratta

Details

In response to this:

/jira refresh
/assign @RishabhSaini
/verified by @rbbratta

Ross tested this on a real baremetal cluster, so we're confident it will do what we need.

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 verified Signifies that the PR passed pre-merge verification criteria label Feb 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@cybertron: This PR has been marked as verified by @rbbratta.

Details

In response to this:

/jira refresh
/assign @RishabhSaini
/verified by @rbbratta

Ross tested this on a real baremetal cluster, so we're confident it will do what we need.

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

openshift-ci Bot commented Feb 25, 2026

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: rbbratta.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

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

3 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 ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rbbratta

In response to this:

/jira refresh
/assign @RishabhSaini
/verified by @rbbratta

Ross tested this on a real baremetal cluster, so we're confident it will do what we need.

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.

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.

@cybertron
Copy link
Copy Markdown
Member

/retest-required

@cybertron
Copy link
Copy Markdown
Member

/assign @RishabhSaini

@cybertron
Copy link
Copy Markdown
Member

/assign @yuqi-zhang

I am told Rishabh is no longer on the MCO team.

Copy link
Copy Markdown
Member

@isabella-janssen isabella-janssen 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, mkowalski, rbbratta

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 May 14, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

@rbbratta: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 521e6b9 into openshift:main May 14, 2026
18 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@rbbratta: Jira Issue Verification Checks: Jira Issue OCPBUGS-63650
✔️ 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-63650 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:

copy connection.lldp to ovs-if-phys0 connection, so we can enable LLDP RX using NetworkManager.

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
Copy link
Copy Markdown
Member

/cherry-pick release-4.22 release-4.21 release-4.20

@openshift-cherrypick-robot
Copy link
Copy Markdown

@cybertron: new pull request created: #6073

Details

In response to this:

/cherry-pick release-4.22 release-4.21 release-4.20

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.

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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants