Bug 1972152

Summary: OCS Operator does not become ready on removing a failed StorageCluster deployment
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: N Balachandran <nibalach>
Component: ocs-operatorAssignee: N Balachandran <nibalach>
Status: VERIFIED --- QA Contact: Aman Agrawal <amagrawa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: muagarwa, nberry, sostapov, tdesala
Target Milestone: ---   
Target Release: OCS 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.8.0-432.ci Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description N Balachandran 2021-06-15 10:52:15 UTC 
Description of problem (please be detailed as possible and provide log
snippets):

The OCS cluster stays in state Not Ready until a storagecluster comes up.
If the storagecluster never comes up successfully (say, due to insufficient resources on the cluster), and is subsequently removed, the ocs operator never moves to Ready


Version of all relevant components (if applicable):

OCS 4.7
OCP 4.7

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


Is there any workaround available to the best of your knowledge?
Yes. Uninstall and reinstall the ocs operator.

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

Is this issue reproducible?
Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create an OCS cluster with insufficient resources to run an OCS storage cluster. (Workers with 4 cpu and 16 GiB RAM)
2. Install the OCS Operator v4.7.0
3. Create a storage cluster - the UI will state that a minimal installation will be performed.
4. Wait for some time for all the OCS pods to come up. Some will stay in Pending state due to the lack of resources. Check the ocs operator status
5. Delete the StorageCluster
6. Check the ocs-operator pod readiness status



Actual results:
The OCS operator does not move to Ready

Expected results:
The OCS operator should move to Ready

Additional info: