-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'helm install' gets tuck in error loop #981
Comments
Can you tell us about the environment that Tiller is running in? Local, remote, GKE, etc? Oh, and the Kubernetes version? I've had that happen once or twice due to k8s API server issues (running k8s 1.3 inside of VirtualBox using |
This could be due to Helm not checking if the pod is ready before connecting. I'll check on it |
FYI, this happens again. We have a cluster with some sort of a networking problem - pods seem to be able to talk to each other but cannot reach outside the flannel network. Trying to install a release on this cluster results in helm getting stuck in a loop:
and tiller pod crashing:
Now of course this is not a valid cluster, but I figured tiller shouldn't just go panic either, and helm should still fail gracefully. |
I have an ansible playbook that:
From time to time, the helm install commands get stuck in an error loop of some sort:
checking kubectl get pods shows that tiller-rc-sf2a4_default is actually present. Could this be a race of some sort between 'helm init' initialising the tiller rc fully and 'helm install' ?
The text was updated successfully, but these errors were encountered: