kubernetes: Namespace stuck on terminating on delete
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): namespace terminating 1.4.6
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report
Kubernetes version (use kubectl version
):
Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.4", GitCommit:"dd6b458ef8dbf24aff55795baa68f83383c9b3a9", GitTreeState:"clean", BuildDate:"2016-08-01T16:45:16Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.6", GitCommit:"e569a27d02001e343cb68086bc06d47804f62af6", GitTreeState:"clean", BuildDate:"2016-11-12T05:16:27Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
- Cloud provider or hardware configuration: GKE
- OS (e.g. from /etc/os-release): Ubuntu 16.04
- Kernel (e.g.
uname -a
): 4.4.0-47-generic - Install tools: N.A
- Others: N.A
What happened: After upgrading our cluster from 1.4.0 to 1.4.6, when deleting a namespace it gets stuck in Terminating.
What you expected to happen: Have the namespace deleted.
How to reproduce it (as minimally and precisely as possible): Upgrade from 1.4.0 to 1.4.6 and delete a namespace.
Anything else do we need to know: I found https://github.com/kubernetes/kubernetes/issues/19317 and https://github.com/kubernetes/kubernetes/issues/37278, but one is specific to thirdpartyresources and the other one to openshift. This issue happens on all namespaces with no special finalizer or thirdpartyresource.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 26 (17 by maintainers)
I am using v1.8.4 and I am having the same problem that deleted namespace stays at “Terminating” forever. I did “kubectl delete namespace XXXX” already.
Still reproducible on 1.5.2. This issues looks like kind of critical 😦
@krmayankk If the namespace is stuck in terminating, usually there should be log entries from the namespace controller in kube-controller-manager.log that indicate why.