Created attachment 1711984 [details] installed-operator Description of problem: Create custom operator with custom catalogsource, the custom operator has same name with a operator in community-operators catalogsource, install one of them into one project, check these operators in operatorhub of the project, both operators are shown with "Installed" status. Version-Release number of selected component (if applicable): 4.6.0-0.nightly-2020-08-18-165040 How reproducible: Always Steps to Reproduce: 1.Create custom operator with custom catalogsource. apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: custom-console-catalogsource-infrasubs namespace: openshift-marketplace spec: sourceType: grpc image: quay.io/yapei/crossplane-operator:mytest displayName: Custom UI Auto Console Testing publisher: OpenShift UI QE 2.Go to OperatorHub page, filter "portw" by keyword, there are two operators filtered out, one is in community-operators catalogsource, the other is custome catalogsource. 3.Choose one of them to install in a project. 4.After installation finished, filter "portw" by keyword on OperatorHub page in the project again. Actual results: 4. Both operators are shown with "Installed". Expected results: 4. Only the operator chosen to install should show "Installed". Additional info:
This is the result of a bug in OLM. See https://bugzilla.redhat.com/show_bug.cgi?id=1814822#c2
Need to determine if we want to try to patch console given the source of the bug is in OLM.
Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1814822 since there is no easy workaround we can apply in the console. *** This bug has been marked as a duplicate of bug 1814822 ***