-
Bug
-
Resolution: Done
-
Undefined
-
None
-
premerge
-
None
-
Low
-
No
-
False
-
Description of problem:
The e2e-metal-ipi-upgrade-ovn-ipv6 job is timing out consistently on the openshift/cluster-baremetal-operator.
This behavior is observed on two PRs targeting the release branches (and not master branch). Examples: https://github.com/openshift/cluster-baremetal-operator/pull/418 and https://github.com/openshift/cluster-baremetal-operator/pull/379
On PR 418, it was found that the 'e2e-metal-ipi-upgrade-ovn-ipv6-baremetalds-e2e-test' pod fails with these logs:
time="2024-05-29T16:38:53Z" level=info msg="event interval matches E2EImagePullBackOff" locator="{Kind map[hmsg:c858c313a8 namespace:e2e-pod-network-disruption-test-vspj5 node:worker-1.ostest.test.metalkube.org pod:pod-network-to-service-disruption-poller-b557744ff-c8vrm]}" message="{BackOff Back-off pulling image \"registry.build05.ci.openshift.org/ci-op-qbhsz0iw/stable@sha256:54b9cd33929ea90a2427ae0f2a098bc75c4d585d88bd92ab495745c8a60d16e8\" map[count:176 firstTimestamp:2024-05-29T15:58:39Z lastTimestamp:2024-05-29T16:38:53Z reason:BackOff]}"
Since this is a non-blocking job, I have kept the Severity as low.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Open a PR for the release-4.16 or release-4.14 branch and run the e2e-metal-ipi-upgrade-ovn-ipv6 job.
Actual results:
Job times out after about 4 hours and 6 minutes.
Expected results:
Job runs to completion (at least sometimes).
Additional info:
