Create this bug to track if manila csi operator appregistry is ready.
Verified fail. When using the registryNamespace: rh-osbs-operators to create catalogsource and deploying the operator: [wduan@MINT OCP]$ oc get csv csi-driver-manila-operator.v4.5.0 -o yaml | grep image image: registry.redhat.io/openshift4/ose-csi-driver-manila-rhel7-operator@sha256:4dbd69aba5adf45477a1bc84f61573a9e01cc4359fdabc6229190dfa7ad9ae0f:latest 1. operator image digest is the not same as in errata https://errata.devel.redhat.com/advisory/54130. 2. ":latest" should be removed I think.
Verified pass with image in https://errata.devel.redhat.com/advisory/54130 [wduan@MINT manila]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-06-16-045437 True False 10h Cluster version is 4.5.0-0.nightly-2020-06-16-045437 After creating operatorsource with registryNamespace: rh-osbs-operators, we can deploy the operator.
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, 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/RHEA-2020:2925