Description of problem (please be detailed as possible and provide log snippests): When trying to delete namespacestores quickly after deleting the buckets that were attached to them, they enter a Rejected state with the following error: "DeleteNamespaceResourceAPI cannot complete because namespace store <name> has buckets attached" Version of all relevant components (if applicable): OCS 4.7.0-268.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No Is there any workaround available to the best of your knowledge? Wait for a while, and retry the deletion Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2 Can this issue reproducible? Yes Can this issue reproduce from the UI? Unknown If this is a regression, please provide more details to justify this: N/A Steps to Reproduce: 1. Create a namespacestore, bucketclass and OBC 2. Delete the OBC, bucketclass and namespacestore in that order, quickly, one after the other (within 3 seconds) 3. Check the status of the namespacestore by using `oc get namespacestore <name> -o yaml` Actual results: The error shows up and the deletion doesn't proceed Expected results: The deletion proceeds as expected Additional info:
Live cluster - https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster/835/ $ get namespacestore NAME TYPE PHASE AGE aws-ns-store-c2b7befc01444b7c9ff11f2f4bf aws-s3 Rejected 14m aws-ns-store-d595c2799e0e452f9aadb0c5bdd aws-s3 Rejected 82s I waited upwards of three hours in the previous cluster - the deletion wouldn't proceed unless I retry it.
Deletion is now instantaneous. OCP 4.7.0-0.nightly-2021-02-22-210958 ocs-operator.v4.7.0-281.ci Verified.
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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, 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/RHSA-2021:2041