Bug 1705117

Note: Bugzilla is forcing me to select OperatorHub sub component in spite of the fact this issue has nothing to do with OperatorHub. It was not possible to leave the Sub Component blank.

Description of problem:

When a user subscribes to an operator with multiple channels and a defaultChannel has not been set for the package then OLM does nothing with the Subscription.


Version-Release number of selected component (if applicable):
Client Version: version.Info{Major:"4", Minor:"0+", GitVersion:"v4.0.0-alpha.0+3bc8da4-1481-dirty", GitCommit:"3bc8da4", GitTreeState:"", BuildDate:"2019-03-05T02:25:42Z", GoVersion:"", Compiler:"", Platform:""}                      
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+6bdc5da", GitCommit:"6bdc5da", GitTreeState:"clean", BuildDate:"2019-05-01T03:59:59Z", GoVersion:"go1.11.8", Compiler:"gc", Platform:"linux/amd64"}

How reproducible: Always


Steps to Reproduce:

Recreation information can be found in https://github.com/djzager/olm-playground/tree/master/scenario3 I used both operator-registry and the ConfigMap method for defining a catalog.

1. (optional) Create namespace scenario3
apiVersion: v1
kind: Namespace
metadata:
  name: scenario3

2. (optional) Create Operator Group in scenario3 namespace
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: example-operator-a
  namespace: scenario3


3. Define ConfigMap with our test operators in openshift-operator-lifecycle-manager namespace

https://raw.githubusercontent.com/djzager/olm-playground/3fefe16d4bb97622c2c698f08836cf7d2731d353/scenario3/configmap/scenario3.configmap.yaml

The portion that is relevant is the packages section:
packages: |-
    - packageName: example-operator-a
      channels:
      - name: alpha
        currentCSV: example-operator-a.v0.0.1
      - name: stable
        currentCSV: example-operator-a.v1.0.0
    - packageName: example-operator-b
      channels:
      - name: alpha
        currentCSV: example-operator-b.v0.0.1
      - name: stable
        currentCSV: example-operator-b.v1.0.0

4. Create a CatalogSource in openshift-operator-lifecycle-manager namespace
https://raw.githubusercontent.com/djzager/olm-playground/3fefe16d4bb97622c2c698f08836cf7d2731d353/scenario3/configmap/scenario3.catalogsource.yaml

5. Create a Subscription to example-operator-a stable channel in scenario3 namespace.
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  generateName: example-operator-a-
  namespace: scenario3
spec:
  channel: stable
  name: example-operator-a
  source: scenario3
  sourceNamespace: openshift-operator-lifecycle-manager


Actual results: Nothing. I could find no evidence of any action taken on the created Subscription.


Expected results: example-operator-a to be installed (as well as example-operator-b to resolve the dependency).


Additional info:

It's worth mentioning that example-operator-a depends on the CRD provided by example-operator-b.

I looked for meaningful information on the status of the Subscription object, the status/logs of the packageserver, catalog operator, olm-operator but was unable to find anything worthwhile.