|Summary:||Shouldn't allow the same packagemanifest objects in the same namespace|
|Product:||OpenShift Container Platform||Reporter:||Jian Zhang <jiazha>|
|Component:||OLM||Assignee:||Evan Cordell <ecordell>|
|Status:||CLOSED ERRATA||QA Contact:||Jian Zhang <jiazha>|
|Version:||4.1.0||CC:||chezhang, dyan, erich, jfan, zitang|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-06-04 10:44:00 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jian Zhang 2019-02-14 06:45:57 UTC
Comment 2 Evan Cordell 2019-04-08 17:53:37 UTC
The objects are not actually created in the same namespace, but they appear because we aggregate across multiple catalog sources. This is expected, but a bit weird. I've moved this to 4.2 as a feature request and tracked it in jira.
Comment 3 Evan Cordell 2019-04-12 18:40:10 UTC
Fixed here: https://github.com/operator-framework/operator-lifecycle-manager/pull/813
Comment 6 Jian Zhang 2019-04-22 05:49:26 UTC
@Evan Verify failed, the same packagemanifest still generated in the same namespace. I followed the steps 1,2,3, got below: mac:~ jianzhang$ oc get packagemanifest -n openshift-marketplace |grep etcd etcd Community Operators 98s etcd Community Operators 120m OLM version: io.openshift.build.commit.id=c718ec855bb26a111d66ba2ba193d30e54f7feb1 Cluster version is 4.1.0-0.nightly-2019-04-22-005054 And, still got the old packagemanifest etcd detail by using `oc get packagemanifest -n openshift-marketplace etcd -o yaml` command. The old one cannot be read successfully. mac:~ jianzhang$ oc get packagemanifest -n openshift-marketplace etcd -o yaml apiVersion: packages.operators.coreos.com/v1 kind: PackageManifest metadata: creationTimestamp: 2019-04-22T03:37:52Z labels: catalog: community-operators catalog-namespace: openshift-marketplace csc-owner-name: community-operators csc-owner-namespace: openshift-marketplace olm-visibility: hidden openshift-marketplace: "true" opsrc-datastore: "true" opsrc-owner-name: community-operators opsrc-owner-namespace: openshift-marketplace opsrc-provider: community provider: Red Hat, Inc. provider-url: "" name: etcd namespace: openshift-marketplace ...
Comment 7 Evan Cordell 2019-04-22 12:20:17 UTC
This is the expected behavior - there are two etcd packages in two different catalogs; unfortunately the extra catalog has the same displayname (so they both appear as "Community Operators") You can see and subscribe to either package by specifying the actual name of the catalog (`installed-community-global-operators` vs `community-operators`) in the `source` field of the Subscription.
Comment 9 Jian Zhang 2019-04-23 10:33:00 UTC
Evan, Thanks for your information! It makes sense, verify it.
Comment 11 errata-xmlrpc 2019-06-04 10:44:00 UTC
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-2019:0758