[scolange@scolange ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-05-17-040457 True False 18m Cluster version is 4.7.0-0.nightly-2021-05-17-040457 [scolange@scolange ~]$ oc get deployment packageserver -n openshift-operator-lifecycle-manager -o yaml | grep "spec:" -A 20 spec: progressDeadlineSeconds: 600 replicas: 2 revisionHistoryLimit: 1 selector: matchLabels: app: packageserver strategy: rollingUpdate: maxSurge: 1 maxUnavailable: 1 type: RollingUpdate template: metadata: annotations: include.release.openshift.io/self-managed-high-availability: "true" olm.operatorGroup: olm-operators olm.operatorNamespace: openshift-operator-lifecycle-manager olm.targetNamespaces: openshift-operator-lifecycle-manager olmcahash: ef59118d42c6514c6c996629f4ee227239a9e0b83311ac04e681fabab7b84e6e creationTimestamp: null LGMT!
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 (Moderate: OpenShift Container Platform 4.7.12 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-2021:1561