Hi Joe,

Thanks for your reminder. We have already tested this situation before the 4.7 release, and it worked as expected, as follows. I'm not sure why you create this issue for the target 4.7.z release. I close it as NOTABUG, please let me know if I missed anything, thanks!

For 4.7.0:
[jzhang@dhcp-140-36 ~]$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0     True        False         53m     Cluster version is 4.7.0
[jzhang@dhcp-140-36 ~]$ oc get catalogsource -n openshift-marketplace community-operators -o=jsonpath={.spec.image}
registry.redhat.io/redhat/community-operator-index:v4.7

For 4.8:
[root@preserve-olm-env data]# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-03-10-142839   True        False         111m    Cluster version is 4.8.0-0.nightly-2021-03-10-142839
[root@preserve-olm-env data]# oc get catalogsource -n openshift-marketplace community-operators -o=jsonpath={.spec.image}
registry.redhat.io/redhat/community-operator-index:v4.7

It was opened because our backport processes require a fix going into 4.6.z to have a corresponding verified fix in 4.7.

Hi Joe, Ben

Thanks for your information! I got it, and change the status to 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 (Moderate: OpenShift Container Platform 4.7.4 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:0957