Version: OCP version: 4.3.0-0.nightly-2020-05-27-224458 [root@preserve-olm-env 1816185]# oc exec catalog-operator-7558695ff7-qmv7s -n openshift-operator-lifecycle-manager -- olm --version OLM version: 0.13.0 git commit: 3740fa3a8aa571ba4ee1f048561d674d4fc6c2d3 Platform: azure Steps to test: 1. Create the community catalog source on platform azure other than aws cat <<EOF > community-operator-catalog.yaml apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: community-operator-catalog namespace: openshift-marketplace spec: displayName: Community Operator Catalog sourceType: grpc image: docker.io/wangzheng422/operator-catalog:community-2020-02-29 publisher: Community EOF oc create -f community-operator-catalog.yaml 2. Check the catalogsource and pod status. [root@preserve-olm-env 1816185]# oc get catsrc -n openshift-marketplace NAME DISPLAY TYPE PUBLISHER AGE community-operator-catalog Community Operator Catalog grpc Community 24m [root@preserve-olm-env 1816185]# oc get pod -n openshift-marketplace NAME READY STATUS RESTARTS AGE community-operator-catalog-zc2lz 1/1 Running 0 24m The community operator catalog pod is running. Verify the bug.
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:2436