Version: [root@preserve-olm-env ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.16 True False 5h Cluster version is 4.5.16 [root@preserve-olm-env ~]# oc exec olm-operator-6b6849569c-8q9n7 -n openshift-operator-lifecycle-manager -- olm --version OLM version: 0.15.1 git commit: 4416b81305fbc1644853796bdfe45bbd9a781643 Steps to verify: 1, Install OCP 4.5 cluster. 2, Check the catalogsource pods in the project openshift-marketplace. [root@preserve-olm-env ~]# oc get pod -n openshift-marketplace NAME READY STATUS RESTARTS AGE certified-operators-7dd654ffbd-sg8q4 1/1 Running 0 5h19m community-operators-67c95b8c9c-gtzzz 1/1 Running 0 5h19m marketplace-operator-c679bd65b-r64lj 1/1 Running 0 5h19m qe-app-registry-5b7fc87f49-n2k7c 1/1 Running 0 5h2m redhat-marketplace-57b5bcd69d-4ktcc 1/1 Running 0 5h19m redhat-operators-768d49b94b-64grt 1/1 Running 0 5h19m There is only one pod for each kind of catalogsource. The bug has been verified.
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.5.17 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-2020:4325