[cloud-user@preserve-olm-env jian]$ oc adm release info registry.ci.openshift.org/ocp/release:4.9.0-0.nightly-2021-11-02-033840 --commits|grep lifecycle operator-lifecycle-manager https://github.com/openshift/operator-framework-olm 6a8cbc2fef0c94bf9455fee0d08e7357b47cef5b [cloud-user@preserve-olm-env jian]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-11-02-033840 True False 4m18s Cluster version is 4.9.0-0.nightly-2021-11-02-033840 [cloud-user@preserve-olm-env jian]$ oc get CronJob -n openshift-operator-lifecycle-manager NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE collect-profiles */15 * * * * False 0 10m 29m [cloud-user@preserve-olm-env jian]$ oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-678f59ffdf-vvx7t 1/1 Running 0 29m collect-profiles-27263925--1-zm4rp 0/1 Completed 0 25m collect-profiles-27263940--1-j779f 0/1 Completed 0 10m olm-operator-f9bf44544-hbqpt 1/1 Running 0 29m package-server-manager-cb545c759-h9gr9 1/1 Running 4 (20m ago) 29m packageserver-84d67ddb7f-d5br6 1/1 Running 0 26m packageserver-84d67ddb7f-s585s 1/1 Running 0 26m The cronjob works well, LGTM, verify it.
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.9.6 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-2021:4119