-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.22
-
None
Description of problem:
Node replacement has been failing since the update job rename patch because the new update jobs have names with a hash we don't look for Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-cluster-etcd-operator-1562-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-techpreview/2031390253415141376
Version-Release number of selected component (if applicable):
4.22 nightlies 3/5/26
How reproducible:
Every recovery job
Steps to Reproduce:
1. Check CI results for jobs that fail with node replacement test timeout out waiting for update job to run
Actual results:
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-cluster-etcd-operator-1562-nightly-4.22-e2e-metal-ovn-two-node-fencing-recovery-techpreview/2031390253415141376
Expected results:
Test passes
Additional info:
- clones
-
-
- POST
-
- links to
