kubernetes build_error ai_generated true

Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress

ID: kubernetes/helm-upgrade-failed-dependency

Also available as: JSON · Markdown · 中文
82%Fix Rate
88%Confidence
1Evidence
2024-01-15First Seen

Root Cause

Helm releases have a pending operation due to a previous incomplete install, upgrade, or rollback, often from a crash or timeout.

generic

中文

Helm 发布版本由于之前的安装、升级或回滚操作未完成（通常由于崩溃或超时）而处于待处理状态。

Official Documentation

https://helm.sh/docs/helm/helm_upgrade/

Workarounds

  1. 80% success Force unlock the release: 'helm rollback <release> <revision> --force' to rollback to a previous revision, which clears the pending state. 
    Force unlock the release: 'helm rollback <release> <revision> --force' to rollback to a previous revision, which clears the pending state.
  2. 85% success Manually delete the pending release secret: 'kubectl delete secret -n <namespace> sh.helm.release.v1.<release>.v<revision>' then retry the upgrade. 
    Manually delete the pending release secret: 'kubectl delete secret -n <namespace> sh.helm.release.v1.<release>.v<revision>' then retry the upgrade.

中文步骤

  1. Force unlock the release: 'helm rollback <release> <revision> --force' to rollback to a previous revision, which clears the pending state.
  2. Manually delete the pending release secret: 'kubectl delete secret -n <namespace> sh.helm.release.v1.<release>.v<revision>' then retry the upgrade.

Dead Ends

Common approaches that don't work:

  1. Run the same upgrade command again with --atomic flag 90% fail

    The pending lock isn't released by retrying; the operation still fails with the same error.

  2. Delete the Helm release and reinstall 50% fail

    Deleting the release loses all release history and secrets; it's destructive and may cause data loss.