[release-4.17] OCPBUGS-43576, SDN-4930: Don't modify pod routes in tests

[openshift-cherrypick-robot]

This is an automated cherry-pick of #29243

/assign tssurya

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-4930

In response to [this](https://github.com/openshift/origin/pull/29250): >This is an automated cherry-pick of #29243 > >/assign tssurya 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.

[jluhrsen]

/retitle [release-4.17] OCPBUGS-43576, SDN-4930: Don't modify pod routes in tests

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-43576, which is valid.

7 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.17.z) matches configured target version for branch (4.17.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-43577](https://issues.redhat.com//browse/OCPBUGS-43577) 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-43577](https://issues.redhat.com//browse/OCPBUGS-43577) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

The bug has been updated to refer to the pull request using the external bug tracker.

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/29250): >This is an automated cherry-pick of #29243 > >/assign tssurya 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.

[knobunc]

/retest /approve /lgtm /label backport-risk-assessed

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc, 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: - ~~[test/extended/networking/OWNERS](https://github.com/openshift/origin/blob/release-4.17/test/extended/networking/OWNERS)~~ [knobunc] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[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-edge-zones	a33c15a0604710ec5656d6d367d0348f728c7c38	link	true	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-azure-ovn-upgrade	a33c15a0604710ec5656d6d367d0348f728c7c38	link	false	/test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	a33c15a0604710ec5656d6d367d0348f728c7c38	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-upgrade	a33c15a0604710ec5656d6d367d0348f728c7c38	link	false	/test e2e-aws-ovn-single-node-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]

/hold

need https://github.com/openshift/origin/pull/29244 to go in first