Description of problem (please be detailed as possible and provide log snippests): When a StorageCluster is deleted, the following items are not removed automatically: 1. StorageClass 2. OCS node labels 3. OCS node taints Version of all relevant components (if applicable): 4.5 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Creating a StorageCluster right after deleting is not possible. Requires manual intervention to clean up the remaining items. Is there any workaround available to the best of your knowledge? Yes, manually deleted the above listed resources. 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: Not a regression Steps to Reproduce: 1. Create a StorageCluster 2. Deleted the StorageCluster Actual results: StorageClasses, Node labels, Node taints aren't removed. Expected results: The above listed resources should be removed. Additional info:
This is manily a BZ describing some aspects of the uninstall epic https://issues.redhat.com/browse/KNIP-1230
providing missing acks after confirming with Raz.
This was done a while ago via: https://github.com/openshift/ocs-operator/pull/556 - storage classes (before FF) https://github.com/openshift/ocs-operator/pull/576 - labels (backport) https://github.com/openshift/ocs-operator/pull/577 - taints (backport)
We should not remove the rack labels since we may or may not have set them. Just like we don't remove the zone lables.
Michael is correct, the rack labels should not be removed. Moving this back to ON_QA.
I think that: since the reason we can't remove the rack labels automatically is to accommodate people who have diverged from the documented install by manually applying the rack labels, we can keep the manual step to remove them in the documentation. Handling that case shouldn't be in the scope of the uninstall documentation until the corresponding install process gets into the install documentation (it might not).
Based on Comment #6 and recent uninstall tests on OCS 4.5.0-521 and 4.5.0-526(rc1) builds, following things are removed in case the storagecluster is deleted: 1. If patched with labelled with cleanup.ocs.openshift.io=yes-really-destroy-data a) The /var/lib/rook directory is cleaned up b) the disk is cleaned up (wipefs)' c) the dataMonDirHostPath is removed Along with this, following entities are removed: d) the OCS storageclasses ocs-storagecluster-ceph-rbd openshift-storage.rbd.csi.ceph.com Delete Immediate true 5d8h ocs-storagecluster-ceph-rgw openshift-storage.ceph.rook.io/bucket Delete Immediate false 5d8h ocs-storagecluster-cephfs openshift-storage.cephfs.csi.ceph.com Delete Immediate true 5d8h Hence, moving the BZ to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Container Storage 4.5.0 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3754
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days