Setting blocker+ according to update in the parent bug.
ipi-on-vsphere, 2 workers cluster, upgrade from 4.10.0-0.nightly-2022-07-16-173050 to 4.11.0-0.nightly-2022-07-16-020951, prometheus-operator-admission-webhook pods and monitoring operator are normal, no issue now # oc get node NAME STATUS ROLES AGE VERSION ***-4g69p-master-0 Ready master 4h50m v1.24.0+9546431 ***-4g69p-master-1 Ready master 4h49m v1.24.0+9546431 ***-4g69p-master-2 Ready master 4h50m v1.24.0+9546431 ***-4g69p-worker-v4l9p Ready worker 4h40m v1.24.0+9546431 ***-4g69p-worker-vr5md Ready worker 4h40m v1.24.0+9546431 # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.nightly-2022-07-16-020951 True False 141m Cluster version is 4.11.0-0.nightly-2022-07-16-020951 # oc get co monitoring NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE monitoring 4.11.0-0.nightly-2022-07-16-020951 True False False 3h59m # oc -n openshift-monitoring get pod -o wide | grep prometheus-operator-admission-webhook prometheus-operator-admission-webhook-67f97cf577-jl2wg 1/1 Running 0 164m 10.128.2.9 ***-4g69p-worker-vr5md <none> <none> prometheus-operator-admission-webhook-67f97cf577-sqzkn 1/1 Running 0 159m 10.131.0.9 ***-4g69p-worker-v4l9p <none> <none> # oc -n openshift-monitoring get deploy prometheus-operator-admission-webhook -oyaml | grep -E "maxUnavailable|maxSurge" maxSurge: 25% maxUnavailable: 1
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069