Verified bug with the build below and i did not revision pruners failing. [knarra@knarra ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.19 True False 11m Cluster version is 4.9.19 [knarra@knarra ~]$ oc get pods -n openshift-kube-scheduler NAME READY STATUS RESTARTS AGE installer-3-ip-10-0-64-23 0/1 Completed 0 25m installer-4-ip-10-0-64-23 0/1 Completed 0 24m installer-5-ip-10-0-52-206 0/1 Completed 0 23m installer-5-ip-10-0-63-232 0/1 Completed 0 22m installer-5-ip-10-0-64-23 0/1 Completed 0 24m installer-6-ip-10-0-52-206 0/1 Completed 0 17m installer-6-ip-10-0-64-23 0/1 Completed 0 18m installer-7-ip-10-0-52-206 0/1 Completed 0 17m installer-7-ip-10-0-63-232 0/1 Completed 0 16m installer-7-ip-10-0-64-23 0/1 Completed 0 15m openshift-kube-scheduler-ip-10-0-52-206 3/3 Running 0 17m openshift-kube-scheduler-ip-10-0-63-232 3/3 Running 0 16m openshift-kube-scheduler-ip-10-0-64-23 3/3 Running 0 15m revision-pruner-7-ip-10-0-52-206 0/1 Completed 0 15m revision-pruner-7-ip-10-0-63-232 0/1 Completed 0 15m revision-pruner-7-ip-10-0-64-23 0/1 Completed 0 15m Based on the above moving bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.21 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0488
*** Bug 2065312 has been marked as a duplicate of this bug. ***
Setting the qe_test_coverage flag to '+' because installations have been automated and the test can be covered via CI