KOTS Deployment Fails With Error: another operation (install/upgrade/rollback) is in progress

Published Date: September 26, 2024 

Products and Versions Covered: 

• Self-hosted, Replicated - KOTS

Summary

When deploying a new sequence from the KOTS Admin Console, the deployment is stuck with a spinning wheel or completes but reports "Deploy failed," and the deploy logs show the error:

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

Resolution

From the application server command line interface:

kubectl get secrets --field-selector type=helm.sh/release.v1

This should return a set of secrets like:

NAME TYPE DATA AGE
sh.helm.release.v1.application.v1 helm.sh/release.v1 1 21d
sh.helm.release.v1.application.v2 helm.sh/release.v1 1 15d

IMPORTANT: The "v2" in "sh.helm.release.v1.application.v2" does not necessarily correspond to the sequence number shown in the KOTS Admin Console. You will need to associate the secrets with the sequence-based, roughly on age.

Next, we will delete the secret(s) associated with problematic sequence(s):

kubectl delete secret sh.helm.release.v1.application.v{i..j}

Replace i with the first secret to delete and j with the last secret. e.g. kubectl delete secret sh.helm.release.v1.application.v{0..4} would delete secrets sh.helm.release.v1.application.v0 through sh.helm.release.v1.application.v4.

Finally, redeploy from the KOTS Admin Console.

Additional Resources 

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.