[release-4.17] SDN-4930: ovn-k, udn crd e2e: Fix status report consumer assertion

[openshift-cherrypick-robot]

This is an automated cherry-pick of #29291

/assign jluhrsen

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-44381 has been cloned as Jira Issue OCPBUGS-44626. Will retitle bug to link to clone. /retitle [release-4.17] OCPBUGS-44626: ovn-k, udn crd e2e: Fix status report consumer assertion

In response to [this](https://github.com/openshift/origin/pull/29301): >This is an automated cherry-pick of #29291 > >/assign jluhrsen Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44626, 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-44381 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead
• expected dependent Jira Issue OCPBUGS-44381 to target a version in 4.18.0, but it targets "4.18" 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](https://github.com/openshift/origin/pull/29301): >This is an automated cherry-pick of #29291 > >/assign jluhrsen Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot Once this PR has been reviewed and has the lgtm label, please assign knobunc for approval. For more information see the Kubernetes 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: - **[test/extended/networking/OWNERS](https://github.com/openshift/origin/blob/release-4.17/test/extended/networking/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[jluhrsen]

/retest

[openshift-ci[bot]]

@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-aws-ovn-kube-apiserver-rollout	048004d40bfad3f1584ec6f43d224ca5783dbeb7	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-serial	048004d40bfad3f1584ec6f43d224ca5783dbeb7	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	048004d40bfad3f1584ec6f43d224ca5783dbeb7	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-upgrade	048004d40bfad3f1584ec6f43d224ca5783dbeb7	link	false	/test e2e-azure-ovn-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[jluhrsen]

/retitle [release-4.17] SDN-4930: ovn-k, udn crd e2e: Fix status report consumer assertion

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.17." or "openshift-4.17.", but it targets "openshift-4.18" instead.

In response to [this](https://github.com/openshift/origin/pull/29301): >This is an automated cherry-pick of #29291 > >/assign jluhrsen Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.