Cluster version is 4.7.0-0.nightly-2020-11-29-133728 [root@preserve-olm-env data]# oc -n openshift-operator-lifecycle-manager exec catalog-operator-7c49448c5d-b8rm6 -- olm --version OLM version: 0.17.0 git commit: 62c86d340fcbfe29bc049766dda52fa232695c35 LGTM, verify it. Didn't encounter this issue during the upgrading from 4.6 to 4.7. [root@preserve-olm-env data]# oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-7c49448c5d-b8rm6 1/1 Running 0 90m olm-operator-74cdc7c6bb-9sbj4 1/1 Running 0 90m packageserver-685876878c-ftjsh 1/1 Running 0 83m packageserver-685876878c-k64hc 1/1 Running 0 83m
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.0 security, bug fix, and enhancement 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-2020:5633
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days