-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19
-
None
-
False
-
Description of problem:
when I run the e2e locally and specify the image to be registry.ci.openshift.org/ocp/release:4.19.0-0.nightly-2025-01-30-091858, The e2e never validates the cluster due to
eventually.go:226: - wanted HostedCluster to desire image registry.ci.openshift.org/ocp/release:4.19.0-0.nightly-2025-01-30-091858, got registry.ci.openshift.org/ocp/release@sha256:daccaa3c0223e23bfc6d9890d7f8e52faa8a5071b2e80d5f753900f16584e3f0even though the hc.status is completed and the desired image matches the history
desired:
image: registry.ci.openshift.org/ocp/release@sha256:daccaa3c0223e23bfc6d9890d7f8e52faa8a5071b2e80d5f753900f16584e3f0
version: 4.19.0-0.nightly-2025-01-30-091858
history:
- completionTime: "2025-01-31T12:45:37Z"
image: registry.ci.openshift.org/ocp/release@sha256:daccaa3c0223e23bfc6d9890d7f8e52faa8a5071b2e80d5f753900f16584e3f0
startedTime: "2025-01-31T12:35:07Z"
state: Completed
verified: false
version: 4.19.0-0.nightly-2025-01-30-091858
observedGeneration: 1
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: