Description of problem: Namespace locked in "Terminating" state. Version-Release number of selected component (if applicable): 4.1.6 How reproducible: unknown Steps to Reproduce: 1. oc delete project codeready 2. oc get projects Actual results: Error from server (Conflict): Operation cannot be fulfilled on namespaces "codeready": The system is ensuring all content is removed from this namespace. Upon completion, this namespace will automatically be purged by the system. Expected results: Project deleted. Additional info: Looking online, there are some issues reported on github regarding this. https://github.com/kubernetes/kubernetes/issues/60807 It seems to be an issue with "finalizers" in the spec of the project. Deleting the line "- kubernetes" via oc edit project does not work. However, doing the following does fix it: https://success.docker.com/article/kubernetes-namespace-stuck-in-terminating Raised to get awareness of it in OpenShift 4.1.z
Can you follow https://docs.google.com/document/d/13YIo4z8r2U5h03cwJVADALHN_dYT0Odp7rgvnUo3TdE/edit?usp=sharing this document, especially the "For Garbage Collector or not able to delete API resources" ?
Created attachment 1608130 [details] log files from controller pods and etcd pods
This is a rather new cluster. it was installed, has been idling for a coule of weeks, then blocked the upgrade that day due to the namespace terminating issue. Nothing is really running on it apart from what is provided by openshift.
Comment on attachment 1608130 [details] log files from controller pods and etcd pods cluster domain name has been replaced with example.com to anonymize the log files.