Description of problem: The Local-storage-operator bundle are pushed into 4.7 index image registry.redhat.io/redhat/redhat-operator-index:v4.7. In the doc https://docs.engineering.redhat.com/display/CFC/Delivery, it said "1.We use a single version to mean a minimum of this version but will be automatically opted-in to the next version 2.‘=’ means a particular version ONLY" So we should use com.redhat.openshift.versions: "=v4.6" in Local-Storage-Operator bundle.Dockerfile Version-Release number of selected component (if applicable): 4.7 How reproducible: Always Steps to Reproduce: 1.Install OCP4.7 2.oc image extract registry.stage.redhat.io/redhat/redhat-operator-index:v4.7 --path /:tmp sqlite3 tmp/database/index.db sqlite> select * from channel where package_name="local-storage-operator"; 4.7|local-storage-operator|local-storage-operator.4.7.0-202102110027.p0 4.6|local-storage-operator|local-storage-operator.4.6.0-202102130032.p0 Actual results: Local-storage-operator 4.6 in redhat-operator-index:v4.7 Expected results: 1.Stop pushing local-storage-operator 4.6 metadata to redhat-operator-index:v4.7. 2.Deprecate 4.6 in production following Accounting to https://docs.engineering.redhat.com/display/CFC/Delivery -> Process for deprecating a bundle Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Waiting for stage testing env.
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.6.23 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:0952