Direct answer
Helm sees the latest release revision as pending. Inspect release history, then roll back or remove only the failed revision when safe.
Where this error appears
Helm upgrade and rollback
Root cause
An interrupted upgrade, client timeout, failed hook, or terminated CI job may leave release metadata in pending-install, pending-upgrade, or pending-rollback.
Minimal reproduction
helm upgrade demo ./chart --wait
# interrupt the process before completionCorrected example
helm history demo -n default
helm rollback demo <last-successful-revision> -n defaultVerify the fix
helm status demo -n default && helm history demo -n defaultThings to check
- Confirm no deployment job is actually still running.
- Avoid deleting every release Secret as the first response.
Authoritative reference
Confirm version-specific behavior in helm history。