Bug 1802089

Referencing original ocs-ci issue https://github.com/red-hat-storage/ocs-ci/issues/1338

One more thing which I found out.

I thought that if I will disable redhat operators source that we will again see the one from Openshift Container Storage but I didn't see any.

apiVersion: config.openshift.io/v1
kind: OperatorHub
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"config.openshift.io/v1","kind":"OperatorHub","metadata":{"annotations":{},"name":"cluster"},"spec":{"sources":[{"disabled":true,"name":"redhat-operators"}]}}
    release.openshift.io/create-only: "true"
  creationTimestamp: "2020-02-12T11:09:29Z"
  generation: 2
  name: cluster
  resourceVersion: "852320"
  selfLink: /apis/config.openshift.io/v1/operatorhubs/cluster
  uid: fc33b32d-a462-4f29-bf84-f0e2f9252529
spec:
  sources:
  - disabled: true
    name: redhat-operators
status:
  sources:
  - disabled: true
    name: redhat-operators
    status: Success
  - disabled: false
    name: certified-operators
    status: Success
  - disabled: false
    name: community-operators
    status: Success





Catalog source is in ready state:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  creationTimestamp: "2020-02-12T11:49:05Z"
  generation: 1
  labels:
    ocs-operator-internal: "true"
  name: ocs-catalogsource
  namespace: openshift-marketplace
  resourceVersion: "808450"
  selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-marketplace/catalogsources/ocs-catalogsource
  uid: 9a9e48b3-384b-466d-a134-9d2366ee44c8
spec:
  displayName: Openshift Container Storage
  icon:
    base64data: ""
    mediatype: ""
  image: quay.io/rhceph-dev/ocs-olm-operator:4.3-308.8ec8be3.release_4.3
  publisher: Red Hat
  sourceType: grpc
status:
  connectionState:
    address: ocs-catalogsource.openshift-marketplace.svc:50051
    lastConnect: "2020-02-13T09:37:41Z"
    lastObservedState: READY
  registryService:
    createdAt: "2020-02-12T11:49:06Z"
    port: "50051"
    protocol: grpc
    serviceName: ocs-catalogsource
    serviceNamespace: openshift-marketplace


But there is no packagemanifest of ocs:
$ oc get packagemanifest -n openshift-marketplace |grep ocs 

this returns nothing.

Not sure where I can get some more details why we do not see packagemanifest.

Please advice

This disappeared packagemanifest we mainly see on cluster deployed over VmWare. Not sure it this can be related somehow to vmware.

*** This bug has been marked as a duplicate of bug 1786471 ***

Hello Vu Dinh,

I see that I forgot to add the example RFE I was trying to mention in the first comment.

What about have feature for disabling specific packages from specific source?


Something like:

apiVersion: config.openshift.io/v1
kind: OperatorHub
metadata:
  name: cluster
spec:
  sources:
  - disabledPackages:
    - ocs-operator
    name: redhat-operators

Do you think it's feasible? If so I will open RFE BZ for that.

This is an interesting suggestion in term of the solution and I can see the reason behind what you suggested. It is technically feasible but the underline issue is there are 2 CatalogSources contain 2 identical packages, not just the OperatorHub itself. The team is aware of this problem. I would recommend you to go ahead with RFE request and we will go from there.

Great, RFE BZ opened here: https://bugzilla.redhat.com/show_bug.cgi?id=1803230