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

Action fails if no release present #12

Open
ks2211 opened this issue Jun 10, 2022 · 0 comments
Open

Action fails if no release present #12

ks2211 opened this issue Jun 10, 2022 · 0 comments

Comments

@ks2211
Copy link

ks2211 commented Jun 10, 2022

We created a new EKS cluster, set up this Github actions in our pipeline.

It was able to assume our EKS role. When it ran the helm upgrade command, we got this error below

Error: UPGRADE FAILED: "release-name" has no deployed releases

It seems like because there is no releases, it fails. I forked the repo and added a --force flag to the shell script and it was able to bypass that error and launch our helm chart.
On subsequent runs, it seems to be fine.

Any thoughts?

I'd ideally like to delete my fork/action and use this (I can submit a PR but would like to know what the best possible option here is).

  • Could include a force option in the with list and pass that flag if that is set
  • google/stackoverflow/GH issues recommends running helm uninstall <release_name> or helm delete <release_name> before running the upgrade command as a possible solution (however running these locally didnt seem to have any affect/builds kept failing until I added the --force option)
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

No branches or pull requests

1 participant