Description of problem:

This is an intermittent defect we observe in the operator install and upgrade. Operator Subscription and CSV can't bind each other. With further investigations, we found it will happen when OLM failed to update the subscription status.

How reproducible:

It can't be reproduced every time, it will appear when subscription status is failed to be updated when installplan is created.

Actual results:

What I observe is the CSV of the operator is created, but there is no update in the subscription status, which cause even if the install plan is completed, the subscription is in the `unknown` status and CSV is in the `Cannot Update` status

Also, it will block the catalog operator reconcile other operators.

Expected results:

I expect the operator could be deployed or upgraded successfully

Additional info:

The root cause is figured out in this github issue: https://github.com/operator-framework/operator-lifecycle-manager/issues/2201