Hide Forgot
verify it on 4.6 oc get clusterversion version -o=jsonpath='{.status.history..version}' 4.6.0-0.nightly-2021-06-11-193006% OLM version: 0.16.1 git commit: cf3f9b212526733cdb2678c947d7a75bbab6c03 cat res.yaml apiVersion: v1 kind: Namespace metadata: name: test-ns --- apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-operator-catalog namespace: test-ns spec: image: quay.io/kuiwang/olm-index:v1945261-a sourceType: grpc --- apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: opencloud-operators namespace: test-ns spec: image: quay.io/kuiwang/olm-index:v1945261 sourceType: grpc --- apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: test-operators namespace: test-ns --- apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: test-subscription namespace: test-ns spec: name: ibm-automation-core channel: v1.0 source: ibm-operator-catalog sourceNamespace: test-ns kubectl apply -f res.yaml namespace/test-ns created catalogsource.operators.coreos.com/ibm-operator-catalog created catalogsource.operators.coreos.com/opencloud-operators created operatorgroup.operators.coreos.com/test-operators created subscription.operators.coreos.com/test-subscription created kubectl get sub -n test-ns NAME PACKAGE SOURCE CHANNEL ibm-common-service-operator-v3-opencloud-operators-test-ns ibm-common-service-operator opencloud-operators v3 test-subscription ibm-automation-core ibm-operator-catalog v1.0 kubectl delete namespace test-ns namespace "test-ns" deleted kubectl get sub -n test-ns NAME PACKAGE SOURCE CHANNEL ibm-common-service-operator-v3-opencloud-operators-test-ns ibm-common-service-operator opencloud-operators v3 test-subscription ibm-automation-core ibm-operator-catalog v1.0 kubectl delete namespace test-ns namespace "test-ns" deleted
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.35 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:2410