helmfile: Workaround for Error: "release-name" has no deployed releases

Since Helm doesn’t allow to install a new release if the old one with the same name is not purged, helm diff shows errors. Thus helmfile apply returns errors too. So, we end up with something like this:

worker 2/17 finished
Error: "shared-alpha-elasticsearch" has no deployed releases
"shared-alpha-elasticsearch" has no deployed releases
Error: plugin "diff" exited with error

worker 6/17 finished
Error: "shared-beta-rabbitmq" has no deployed releases
"shared-beta-rabbitmq" has no deployed releases
Error: plugin "diff" exited with error

worker 3/17 finished
Error: "shared-dev-elasticsearch" has no deployed releases
"shared-dev-elasticsearch" has no deployed releases
Error: plugin "diff" exited with error

Do you any thoughts on how to work around this?

About this issue

Original URL
State: open
Created 5 years ago
Reactions: 5
Comments: 18 (10 by maintainers)

Most upvoted comments

I solved my issue by making sure that the previous install was purged completely: helm delete hello-python --purge. After that, helmfile is deploying successfully

+12

pdutta777 on Feb 12, 2019

Helm’s --atomic flag introduced in 2.13 will purge an initial release if it fails for whatever reason meaning subsequent installs will succeed

https://github.com/roboll/helmfile/pull/491 aims to support this as a configurable option for Helmfile releases

Evesy on Mar 14, 2019

The only fix I came up with is to do a delete --purge before reapplying but it’s not an ideal solution.

Edit: just found your post, https://github.com/databus23/helm-diff/issues/121#issuecomment-462047382 , not sure if my answer is really relevant 😕

aslafy-z on Feb 9, 2019