Note: It was not possible to leave the Sub Component blank. This issue is specific to OLM but not necessarily related to OperatorHub.

Description of problem:

When a user subscribes to an operator that "required" the CRD that is provided by another operator, OLM generates a subscription to that operator. Unfortunately, when the InstallPlan completes the status of the generated Subscription is never updated. The consequence of this is that when updates become available for the dependent operator, they are not taken/installed.

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:
Everything needed to reproduce this issue can be found here -- https://github.com/djzager/olm-playground/tree/master/scenario2

I attempted with operator-registry and configmap based catalogs.

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

2. (optional) Create Operator Group in scenario2 namespace
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: scenario2
  namespace: scenario2

3. Create ConfigMap with operator catalog in openshift-operator-lifecycle-manager namespace
https://raw.githubusercontent.com/djzager/olm-playground/d3edd369ca7fd1e800c2dd096f57ebc67eeb6545/scenario2/configmap/scenario2-v1.configmap.yaml

Two operators with one channel (alpha) AND one version (v0.0.1)

  packages: |-
    - packageName: example-operator-a
      channels:
      - name: alpha
        currentCSV: example-operator-a.v0.0.1
    - packageName: example-operator-b
      channels:
      - name: alpha
        currentCSV: example-operator-b.v0.0.1

4. Create CatalogSource in openshift-operator-lifecycle-manager namespace
https://raw.githubusercontent.com/djzager/olm-playground/d3edd369ca7fd1e800c2dd096f57ebc67eeb6545/scenario2/configmap/scenario2.catalogsource.yaml

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

6. See that the InstallPlan is complete
$ kubectl get installplan -n scenario2 install-bfcbm -o go-template='{{ .status.phase }}'
Complete

7. Check the Subscriptions in scenario2 namespace
$ kubectl get subscriptions -n scenario2 -o go-template='{{ range .items }}{{ .metadata.name }}{{ " -- " }}{{ .status.state }}{{ "\n" }}{{ end }}'                                                              
example-operator-a-nn2r6 -- AtLatestKnown
example-operator-b-alpha-scenario2-openshift-operator-lifecycle-manager -- UpgradePending

8. Update the scenario2 ConfigMap in openshift-operator-lifecycle-manager namespace
https://raw.githubusercontent.com/djzager/olm-playground/d3edd369ca7fd1e800c2dd096f57ebc67eeb6545/scenario2/configmap/scenario2-v2.configmap.yaml

There is now a new CSV available for example-operator-b

  packages: |-
    - packageName: example-operator-a
      channels:
      - name: alpha
        currentCSV: example-operator-a.v0.0.1
    - packageName: example-operator-b
      channels:
      - name: alpha
        currentCSV: example-operator-b.v0.0.2

Actual results: No change.


Expected results: For example-operator-b deployment to be upgraded and using docker.io/djzager/example-operator-b:v2