Description of problem: Project local-storage stuck in terminating status. The project is used for deploy/undeploy local storage. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-07-21-222447 How reproducible: Not sure Steps to Reproduce: 1.Following https://github.com/openshift/local-storage-operator/blob/master/docs/deploy-with-olm.md#deploy-local-storage-operator 2.Run command `oc delete project local-storage`. Actual results: The project stuck in terminating status, though nothing show in the project. Expected results: Things are clean-up. Or There is a way to manually recover/clean-up everything. Additional info: $ oc get project local-storage NAME DISPLAY NAME STATUS local-storage Terminating $ oc apply -f catalog-create-subscribe.yaml Error from server (Forbidden): error when creating "catalog-create-subscribe.yaml": operatorgroups.operators.coreos.com "local-operator-group" is forbidden: unable to create new content in namespace local-storage because it is being terminated Error from server (Forbidden): error when creating "catalog-create-subscribe.yaml": catalogsources.operators.coreos.com "local-storage-manifests" is forbidden: unable to create new content in namespace local-storage because it is being terminated Error from server (Forbidden): error when creating "catalog-create-subscribe.yaml": subscriptions.operators.coreos.com "local-storage-subscription" is forbidden: unable to create new content in namespace local-storage because it is being terminated $ oc status In project local-storage on server https://api_qe_cluster:6443 You have no services, deployment configs, or build configs. Run 'oc new-app' to create an application. $ oc get all No resources found.
This is a known issue - https://github.com/operator-framework/operator-sdk/issues/1503 The workaround for now is: 1. To not do that. 2. Or to remove the finalizer manually from localvolume CR that exists in `local-storage` namespace. Which will cause localvolume CR to deleted and namespace will be removed. We will document this behaviour.
*** Bug 1820175 has been marked as a duplicate of this bug. ***
*** Bug 1820178 has been marked as a duplicate of this bug. ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days