Cluster version is 4.6.0-0.nightly-2020-12-14-015205
[root@preserve-olm-env data]# oc -n openshift-operator-lifecycle-manager exec catalog-operator-6bc7d9ff89-rnszx -- olm --version
OLM version: 0.16.1
git commit: fe32277830b3dc086e014c0e3391de671e5f49f4
LGTM, verify it. The catalog-operator works well, no crash found.
[root@preserve-olm-env data]# oc get pods -n openshift-operator-lifecycle-manager
NAME READY STATUS RESTARTS AGE
catalog-operator-6bc7d9ff89-rnszx 1/1 Running 0 3h34m
olm-operator-748968646f-tqk76 1/1 Running 0 3h34m
packageserver-6cf594f9fc-8ml89 1/1 Running 0 3h28m
packageserver-6cf594f9fc-9rx8n 1/1 Running 0 3h28m
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.6.9 security and 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.