Skip to content
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

helmfile destroy fails, needs concurrency flag #690

Closed
Morriz opened this issue Jun 13, 2019 · 12 comments · Fixed by #691
Closed

helmfile destroy fails, needs concurrency flag #690

Morriz opened this issue Jun 13, 2019 · 12 comments · Fixed by #691

Comments

@Morriz
Copy link

Morriz commented Jun 13, 2019

A global helmfile destroy gives errors for some charts. If I destroy them one after the other with helmfile -l name=$release destroy I see no errors.

I suspect something is conflicting because of the attempted concurrency, and therefor I would like the destroy command to also honour --concurrency=1.

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 13, 2019

@Morriz Hey! Mind sharing the error message you saw?

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

Yeah, this is what I get (not revealing anything):

err: release "ingress" failed: helm exited with status 143:
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 114: 88849 Terminated: 15          [[ "${HELM_TILLER_SILENT}" == "false" ]]
  Error: plugin "tiller" exited with error
err: release "external-dns" failed: helm exited with status 143:
  Error: transport is closing
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 128: 88799 Terminated: 15          ./bin/tiller --storage=secret --listen=127.0.0.1:${HELM_TILLER_PORT}  (wd: ~/.helm/plugins/helm-tiller)
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 114: 88851 Terminated: 15          [[ "${HELM_TILLER_SILENT}" == "false" ]]
  Error: plugin "tiller" exited with error
err: release "ingress-merge" failed: helm exited with status 1:
  Error: transport is closing
  Error: plugin "tiller" exited with error
changing working directory back to "/Users/Morriz/Documents/Workspace/essent/k8s-stacks"
in helmfile.d/helmfile-ingress.yaml: 3 errors:
err 0: release "ingress" failed: helm exited with status 143:
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 114: 88849 Terminated: 15          [[ "${HELM_TILLER_SILENT}" == "false" ]]
  Error: plugin "tiller" exited with error
err 1: release "external-dns" failed: helm exited with status 143:
  Error: transport is closing
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 128: 88799 Terminated: 15          ./bin/tiller --storage=secret --listen=127.0.0.1:${HELM_TILLER_PORT}  (wd: ~/.helm/plugins/helm-tiller)
  /Users/Morriz/.helm/plugins/helm-tiller/scripts/tiller.sh: line 114: 88851 Terminated: 15          [[ "${HELM_TILLER_SILENT}" == "false" ]]
  Error: plugin "tiller" exited with error
err 2: release "ingress-merge" failed: helm exited with status 1:
  Error: transport is closing
  Error: plugin "tiller" exited with error

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

I don't see what is going wrong in the tiller-plugin on that line 114 or 128

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

Yeah, it seems the plugin tries to stop the local tiller but others processes are using it of course.

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

so please add --concurrency flag ;)

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 13, 2019

@Morriz Ah, that seems like the current restriction of the helm-tiller integration #449

Tiller needs two or three ports to bind, grpc, metrics, and optionally trace ports. The error seems to be due to that grpc and metrics ports are conflicting across tiller instances. So yes, the shortterm solution would be to add --concurrency :) Ok

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

tnx....it would be nicer if the plugin would allow for concurrency...I will create a request for that

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 13, 2019

@Morriz Please try #691!

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

I would love to, but where can I find the master binary?

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 13, 2019

Just grab the latest binary from github releases.

@Morriz
Copy link
Author

Morriz commented Jun 13, 2019

0.77 works great now...mega tnx for the quick update!

@mumoshu
Copy link
Collaborator

mumoshu commented Jun 16, 2019

Glad to help! Thanks for your confirmation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants