Helm "another operation is in progress" (pending-upgrade) in CI - Fix it

By Kaveh Alemi·Latchkey

Helm marks a release pending-install/pending-upgrade/pending-rollback while an operation runs. If the process was killed (CI cancelled, timeout, OOM) the release stays pending and Helm refuses to start a new operation, treating it as concurrent.

What this error means

helm upgrade fails with Error: another operation (install/upgrade/rollback) is in progress. helm status shows a pending-* state with no active run.

helm

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

Common causes

Interrupted previous run

A cancelled or killed Helm process left the release in a pending state without completing or rolling back.

Genuine concurrent run

Two pipelines operate on the same release at once.

How to fix it

Clear the stuck pending state

Roll back to the last good revision, which releases the lock.

Terminal

helm status api
helm history api
helm rollback api <last-deployed-revision>

Recover when no good revision exists

If only a failed first install is pending, helm uninstall api then reinstall.
Ensure no other pipeline is mid-operation before clearing.
Re-run the upgrade once the release is in a deployed/clean state.

How to prevent it

Serialize Helm operations per release; never run two concurrently.
Use --atomic --timeout so interrupted runs roll back instead of hanging pending.
Add adequate timeouts so CI does not kill Helm mid-operation.

Frequently asked questions

What causes ""another operation (install/upgrade/rollback) is in progress""?