Hi Soumi, I am looking at all the details like what steps the customer took before reaching here. I am seeing there's no ocs-operator or any related csvs present. The storagecluster cr is in phase progressing and has no deletion timestamp but the storagesystem has one. This means when the stopragesystem deletion happened ocs operator pod was no longer present. As there are no ocs-operator pod, no rook-ceph-operator pod, no noobaa-operator pod the storagecluster deletion won't work. I am not sure how they deleted these pods/csvs/subs, the uninstall doc here https://access.redhat.com/articles/6525111 doesn't say anywhere to delete the ocs/odf/noobaa/rook related pods or csvs or subs. And in the case discussion as well I couldn't find any reason why they have deleted these pods/csvs. if they have done that mistakenly then they can go ahead & install the odf operator from the UI. Which will bring the required pods for the uninstall to go through. But first confirm the reason of deletion of the odf related subs/csvs/pods.
Hi Soumi, I can see the storagesystem/storagecluster deletion has gone through. The storagecluster & storagesystem are no longer stuck there. There are no pods relating to the storagecluster present. The customer can now go ahead and follow the steps for uninstallation.
Glad to know the issue is resolved. Closing this.