[release-4.21] OCPBUGS-83422: wait for patch port to apply drop garp flows by openshift-cherrypick-robot · Pull Request #2946 · openshift/cluster-network-operator

openshift-cherrypick-robot · 2026-03-27T20:39:48Z

This is an automated cherry-pick of #2910

/assign bpickard22

There is currently a race in the ovnkube-lib script where we try to add some drop flows to prevent duplicate garps to the patch port, but if the patch port isnt ready, the ovn-controller can connect to the db and create the patch port without the flow. We need to wait for the patch port to exist before we try to add the GARP drop flow Will log success on flow write, one wait at 30 seconds if we end up waiting that long, and a failure if we run out of retries (will try for 180 seconds - 90 times w/ 2 second sleep between tries) Assisted-By: Claude Sonnet 4.5 Signed-off-by: Benjamin Pickard <bpickard@redhat.com>

coderabbitai · 2026-03-27T20:39:57Z

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6381b875-285c-4da9-8ead-ce6252277ca9

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

jluhrsen · 2026-04-01T21:02:38Z

/close

openshift-ci · 2026-04-01T21:03:10Z

@jluhrsen: Closed this PR.

Details

In response to this:

/close

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.

jluhrsen · 2026-04-01T21:03:17Z

/reopen

openshift-ci · 2026-04-01T21:03:30Z

@jluhrsen: Reopened this PR.

Details

In response to this:

/reopen

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-ci-robot · 2026-04-01T21:03:35Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77015, which is invalid:

expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
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 Jira Issue OCPBUGS-77015 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

This is an automated cherry-pick of #2910

/assign bpickard22

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.

bpickard22 · 2026-04-14T15:45:51Z

/retitle [release-4.21] OCPBUGS-83422: wait for patch port to apply drop garp flows

openshift-ci-robot · 2026-04-14T15:46:01Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-83422, 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 Jira Issue OCPBUGS-83422 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

This is an automated cherry-pick of #2910

/assign bpickard22

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.

bpickard22 · 2026-04-14T15:46:07Z

/jira refresh

openshift-ci-robot · 2026-04-14T15:46:12Z

@bpickard22: This pull request references Jira Issue OCPBUGS-83422, 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 Jira Issue OCPBUGS-83422 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

bpickard22 · 2026-04-14T15:47:28Z

/jira refresh

openshift-ci-robot · 2026-04-14T15:47:36Z

@bpickard22: This pull request references Jira Issue OCPBUGS-83422, 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.21.z) matches configured target version for branch (4.21.z)
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-77015 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-77015 targets the "4.22.0" version, which is one of the valid target versions: 4.22.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.

bpickard22 · 2026-04-14T16:02:43Z

/retest

openshift-ci · 2026-04-14T21:50:35Z

@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-vsphere-ovn-dualstack-primaryv6	`76e5c5c`	link	false	`/test e2e-vsphere-ovn-dualstack-primaryv6`
ci/prow/e2e-openstack-ovn	`76e5c5c`	link	false	`/test e2e-openstack-ovn`
ci/prow/e2e-azure-ovn-dualstack	`76e5c5c`	link	false	`/test e2e-azure-ovn-dualstack`
ci/prow/qe-perfscale-aws-ovn-small-node-density-cni	`76e5c5c`	link	false	`/test qe-perfscale-aws-ovn-small-node-density-cni`
ci/prow/security	`76e5c5c`	link	false	`/test security`
ci/prow/e2e-aws-hypershift-ovn-kubevirt	`76e5c5c`	link	false	`/test e2e-aws-hypershift-ovn-kubevirt`

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.

weliang1 · 2026-04-15T03:04:51Z

/verified by @weliang1

openshift-ci-robot · 2026-04-15T03:05:03Z

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

Details

In response to this:

/verified by @weliang1

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.

danwinship · 2026-04-16T16:17:13Z

/lgtm
/backport-risk-assessed

openshift-ci · 2026-04-16T16:17:36Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

~~OWNERS~~ [danwinship]

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

sdodson · 2026-04-17T18:13:23Z

/label backport-risk-assessed

Per @danwinship comment above

openshift-merge-bot · 2026-04-17T19:03:26Z

/retest-required

Remaining retests: 0 against base HEAD 259ea6b and 2 for PR HEAD 76e5c5c in total

openshift-ci-robot · 2026-04-17T20:43:12Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-83422
✔️ 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-83422 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:

This is an automated cherry-pick of #2910

/assign bpickard22

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 · 2026-04-18T14:56:24Z

Fix included in release 4.21.0-0.nightly-2026-04-18-041410

openshift-cherrypick-robot assigned bpickard22 Mar 27, 2026

openshift-cherrypick-robot mentioned this pull request Mar 27, 2026

OCPBUGS-77015: wait for patch port to apply drop garp flows #2910

Merged

openshift-ci bot closed this Apr 1, 2026

openshift-ci bot reopened this Apr 1, 2026

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 Apr 1, 2026

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

openshift-ci bot changed the title ~~[release-4.21] OCPBUGS-77015: wait for patch port to apply drop garp flows~~ [release-4.21] OCPBUGS-83422: wait for patch port to apply drop garp flows Apr 14, 2026

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 Apr 14, 2026

openshift-ci bot requested a review from anuragthehatter April 14, 2026 15:47

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

openshift-ci bot assigned danwinship Apr 16, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 17, 2026

openshift-ci bot assigned anuragthehatter, asood-rh, barbora137, imatza-rh, jechen0648, mffiedler, rbbratta and weliang1 Apr 17, 2026

openshift-merge-bot bot merged commit bf38adb into openshift:release-4.21 Apr 17, 2026
47 of 53 checks passed

Conversation

openshift-cherrypick-robot commented Mar 27, 2026

Uh oh!

coderabbitai bot commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

jluhrsen commented Apr 1, 2026

Uh oh!

openshift-ci bot commented Apr 1, 2026

Uh oh!

jluhrsen commented Apr 1, 2026

Uh oh!

openshift-ci bot commented Apr 1, 2026

Uh oh!

openshift-ci-robot commented Apr 1, 2026

Uh oh!

bpickard22 commented Apr 14, 2026

Uh oh!

openshift-ci-robot commented Apr 14, 2026

Uh oh!

bpickard22 commented Apr 14, 2026

Uh oh!

openshift-ci-robot commented Apr 14, 2026

Uh oh!

bpickard22 commented Apr 14, 2026

Uh oh!

openshift-ci-robot commented Apr 14, 2026

Uh oh!

bpickard22 commented Apr 14, 2026

Uh oh!

openshift-ci bot commented Apr 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

weliang1 commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

danwinship commented Apr 16, 2026

Uh oh!

openshift-ci bot commented Apr 16, 2026

Uh oh!

sdodson commented Apr 17, 2026

Uh oh!

openshift-merge-bot bot commented Apr 17, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Uh oh!

openshift-merge-robot commented Apr 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

15 participants

coderabbitai bot commented Mar 27, 2026 •

edited

Loading

openshift-ci bot commented Apr 14, 2026 •

edited

Loading