Description of problem:

When I make a Subscription that references an unknown startingCSV, the subscription resource appears to be 'stuck' indefinitely and never gains a status. Meanwhile, the catalog operator logs (which a user would have no idea where to look for) contain the error message i'm looking for:

Version-Release number of selected component (if applicable):

4.1.0

How reproducible:


Make a subscription with a startingCSV field that will not resolve:


$ oc get subscriptions -n federation-test -o yaml
apiVersion: v1
items:
- apiVersion: operators.coreos.com/v1alpha1
  kind: Subscription
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"operators.coreos.com/v1alpha1","kind":"Subscription","metadata":{"annotations":{},"name":"namespaced-federation-sub","namespace":"federation-test"},"spec":{"channel":"alpha","name":"federation","source":"federation","sourceNamespace":"openshift-operator-lifecycle-manager","startingCSV":"federation.v0.0.8"}}                                                                                          
    creationTimestamp: 2019-04-30T20:42:08Z
    generation: 1
    name: namespaced-federation-sub
    namespace: federation-test
    resourceVersion: "131061"
    selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/federation-test/subscriptions/namespaced-federation-sub                                                                                              
    uid: 6bd08b84-6b88-11e9-8a4b-02f19f25e6f8
  spec:
    channel: alpha
    name: federation
    source: federation
    sourceNamespace: openshift-operator-lifecycle-manager
    startingCSV: federation.1.2.3
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


... the subscription will never gain a status.

Steps to Reproduce:

1.
2.
3.

Actual results:

Subscription's status should reflect when there is a problem preventing the subscription from being serviced.

Expected results:

Subscription's status is never updated.

Additional info: