Description of problem: The csv container-security-operator.v1.0.0 metadata refer to the image which does not exist on the quay.io Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-19-122017 How reproducible: Always Steps to Reproduce: 1. create cso catalogsource $ cat cso.catalogsource.yaml apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: container-security-operator spec: sourceType: grpc image: quay.io/quay/cso-catalog@sha256:5c7faaf489824ac357d418aa2840906dae209bf55b3a7bdebe15fee0d50349e5 $ oc create -f cso.catalogsource.yaml 2. goto operatorHub page -> install container Security Operator on webconsole for all namespaces. 3. oc get po container-security-operator-794cd6656-xzqq2 -n openshift-operators Actual results: Failed to pull image "quay.io/quay/container-security-operator@sha256:2ec82e78dd81f17b3ff2a5665ea3f717b69b7fddd05516a2efdf1736bbf1660a": rpc error: code = Unknown desc = Error reading manifest sha256:2ec82e78dd81f17b3ff2a5665ea3f717b69b7fddd05516a2efdf1736bbf1660a in quay.io/quay/container-security-operator: manifest unknown: manifest unknown Error: ImagePullBackOff Expected results: The csv should refer to the existing images. Additional info: when I update 'image' of deployment to "quay.io/quay/container-security-operator:latest" . it works well.
This has been fixed with the most recent version of `master` for `container-security-operator`.
The csv should refer to the existing images now. 4.3.0-0.nightly-2019-11-29-051144
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/RHBA-2020:0062