UPSTREAM: <carry>: fix e2e test failure

[sairameshv]

Encountered an issue while performing the rebase of k8s 1.29

This change might fix the issue.

[openshift-ci-robot]

@sairameshv: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• e9cc160|UPSTREAM: : fix e2e test failure: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[sairameshv]

/hold
/test e2e-aws-ovn-cgroupsv2

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sairameshv
Once this PR has been reviewed and has the lgtm label, please assign mfojtik 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:

• DOWNSTREAM_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]

@sairameshv: 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/integration	e9cc160	link	true	/test integration
ci/prow/e2e-aws-crun-wasm	e9cc160	link	true	/test e2e-aws-crun-wasm

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/test-infra repository. I understand the commands that are listed here.

[jmguzik]

/payload 4.16 nightly blocking

[openshift-ci]

@jmguzik: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16

• periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-sdn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.16-upgrade-from-stable-4.15-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.16-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-sdn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ce89da10-98d9-11ee-9f72-922ec3b9295c-0

[jmguzik]

/payload 4.15 nightly blocking

[openshift-ci]

@jmguzik: trigger 9 job(s) of type blocking for the nightly release of OCP 4.15

• periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-sdn-upgrade
• periodic-ci-openshift-release-master-ci-4.15-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.15-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-ovn-dualstack
• periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-sdn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0a95bff0-98db-11ee-8706-f74c3e65da6f-0

[harche]

/payload periodic-ci-openshift-release-master-nightly-4.16-e2e-metal-ipi-ovn-ipv6

[openshift-merge-robot]

PR needs rebase.

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/test-infra repository.

[sairameshv]

I doubt this could be an issue and I would like to track this upstream separately. Hence, closing the PR