Description of problem: In the local storage operator csv's description, it set the containerImage like "quay.io/openshift/origin-local-storage-operator:4.2.0". It's very easy to mislead the user to think we use the upstream image in OCP. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2020-03-09-194140 How reproducible: 100% Steps to Reproduce: 1. Install local storage operator from webconsole. 2. 3. Actual results: The image in csv description is: oc get csv local-storage-operator.4.2.23-202003090920 -ojson| jq .metadata|grep containerImage "containerImage": "quay.io/openshift/origin-local-storage-operator:4.2.0", The real image used is: $ oc get csv local-storage-operator.4.2.23-202003090920 -ojson| jq .spec.install.spec.deployments[0].spec.template.spec.containers[0].image "registry.stage.redhat.io/openshift4/ose-local-storage-operator@sha256:78ff8412e2c82c55b0b59e186ec5bbbda6ca7e0b248ac83cb10f2ff2227a85e4" Expected results: The image in the description should be the image used. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: $ oc get packagemanifests local-storage-operator -oyaml|grep -i image containerImage: quay.io/openshift/origin-local-storage-operator:4.2.0 containerImage: quay.io/openshift/origin-local-storage-operator:4.2.0 containerImage: quay.io/openshift/origin-local-storage-operator:4.3.0 From this looks like we use the upstream images in OCP.
Verified with: nightly build: 4.5.0-0.nightly-2020-03-25-223812 CSV version: local-storage-operator.4.5.0-202003181016
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 image release advisory), 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:2409