Found during ocs-ci run for odf-4.19 to odf-4.20 upgrade.

Identification that the bug is hit is StorageConsumer (internal) .spec.enable is set to true but StorageClient (ocs-storagecluster) .status is empty, expected is .status should be set with storageconsumer uid w/ Connected phase.

Usual symptoms are no ocs storageclasses are created and noobaa db pvs stay in pending.

The issue is non-reproducible due to race conditions and workaround is to update the storageclient status w/ storageconsumer info till the fix is delivered, like

> k get storageconsumer internal -oyaml | yq -r .metadata.uid
3be58545-6dbb-44ef-9b34-cdaba9e40031

--- update below fields w/ above info
> k get storageclient ocs-storagecluster -oyaml | yq -r .status
id: 3be58545-6dbb-44ef-9b34-cdaba9e40031
phase: Connected

Able to deliver the fix in a build should be considered as the verification w/ no extra validation required by QE.