helm: Helm 3.5.0 releases disappear if timed out
How to reproduce:
- Do
helm upgradecommand, and set--timeout(with some value) and--waitflags. - Press CTRL+C to terminate the helm upgrade operation.
- The
helm upgradecommand will fail. - Do
helm lscommand, and now you won’t be able to see the release. - Try to do
helm upgradecommand again for this release. - You will get the following error:
another operation (install/upgrade/rollback) is in progress.
What I would expect: I would expect that the release will be in a “failed” state, and won’t disappear from the releases list. In addition, I would expect that the second helm upgrade would work, and fix the release to the desired state.
Why I would expect that:
Releases may fail from time to time due to timeouts or abruptions, and retrying helm upgrade command is the desired solution in these cases.
A workaround:
If you get another operation (install/upgrade/rollback) is in progress error, you can rollback/delete the release, and then do helm upgrade command again. However, as I stated, I don’t think this is the desired behavior.
Cloud Provider/Platform (AKS, GKE, Minikube etc.): AKS
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 15 (1 by maintainers)
Some news on this?
You’re right @Alien2150, it disappears, but if know the name of the missing release, rolling it back will restore it. It’s not the ideal solution, but it’s the best we can do until the issue is fixed.
Will try next time @guy-microsoft. Was not seeing the release anymore
@Alien2150
helm rollbackworked for me as an alternative to deleting the secret.@bacongobbler, yes:
I checked it more deeply, and I think that the issue happens when the helm client closes the connection with the cluster (for example, when you press CTRL+C during helm upgrade with wait).
I’m updating my issue with a more accurate description.