Created attachment 2046271 [details]
NooBaa core pod showing scheduling error

Description of problem (please be detailed as possible and provide log
snippests):
When MCG standalone is deployed with ODF >=4.15, noobaa pods can not be scheduled and install does not complete.

When MCG standalone cluster is upgraded from ODF 4.14 to ODF >=4.15, noobaa pods can not be scheduled and upgrade does not complete.

Until ODF 4.14, we were not required to label the nodes with ODF label `cluster.ocs.openshift.io/openshift-storage: ''` for MCG standalone mode. But, ODF 4.15 onwards a change was made that forces us to either label the nodes with the default ODF label `cluster.ocs.openshift.io/openshift-storage: ''` or provide our custom node selector label via StorageCluster CR. This is a change in default behavior.

Version of all relevant components (if applicable):
ODF 4.15 and above

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes. MCG becomes unsuable.

Is there any workaround available to the best of your knowledge?
Yes, we can label the worker nodes with default ODF label `cluster.ocs.openshift.io/openshift-storage: ''` .

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
This is a regression from the default behavior in 4.14.

Steps to Reproduce:
1. Deploy ODF 4.16
2. Make sure nodes do not have the label `cluster.ocs.openshift.io/openshift-storage: ''`
3. Deploy MCG standalone mode

or
1. Deploy ODF 4.14
2. Make sure nodes do not have the label `cluster.ocs.openshift.io/openshift-storage: ''`
3. Deploy MCG standalone mode
4. Upgrade to ODF 4.15

Actual results:
Install/upgrade does not complete.

Expected results:
Install/upgrade does completes without errors.

Additional info: