[release-4.18] OCPBUGS-62671: Add drop flows for GARP

[martinkennelly]

while ovnkube-controller is processing.
Its removed by ovnkube-controller when processing
complete.

(cherry picked from commit 5720e33) (cherry picked from commit 22ff5c1)

[openshift-ci-robot]

@martinkennelly: This pull request references Jira Issue OCPBUGS-62671, which is invalid:

• expected Jira Issue OCPBUGS-62671 to depend on a bug targeting a version in 4.19.0, 4.19.z 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.

In response to this:

while ovnkube-controller is processing.
Its removed by ovnkube-controller when processing
complete.

(cherry picked from commit 5720e33) (cherry picked from commit 22ff5c1)

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: martinkennelly
Once this PR has been reviewed and has the lgtm label, please assign danwinship for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@martinkennelly: This PR was included in a payload test run from openshift/machine-config-operator#5325
trigger 10 job(s) of type blocking for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0d396b30-9f8c-11f0-90d0-4678c9c2c425-0

[martinkennelly]

/hold until qe verifys

@pliurh can you review this please since you reviewed the higher version and add the necessary labels. Its a critical bug. Clean cherry-pick. Thank you.

[martinkennelly]

/retest

I saw the following disruption error on upgrade - its probably unrelated to this PR but i wanted to post it here incase we see it again:

{  backend-disruption-name/oauth-api-reused-connections connection/reused disruption/openshift-tests was unreachable during disruption:  for at least 14s (maxAllowed=10s):

[openshift-ci]

@martinkennelly: 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/4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade	c5aacca	link	false	/test 4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
ci/prow/security	c5aacca	link	false	/test security
ci/prow/e2e-aws-hypershift-ovn-kubevirt	c5aacca	link	false	/test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-openstack-ovn	c5aacca	link	false	/test e2e-openstack-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.