Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to recover from Error: another operation (install/upgrade/rollback) is in progress #475

Open
krassowski opened this issue Jun 4, 2024 · 1 comment

Comments

@krassowski
Copy link
Member

krassowski commented Jun 4, 2024

If the helm chart upgrade is interrupted the Error: another operation (install/upgrade/rollback) is in progress operation persists preventing further deployment. It should be possible to recover from this by executing a helm rollback command. I do not know how to execute this command

Cf- https://stackoverflow.com/questions/71599858/upgrade-failed-another-operation-install-upgrade-rollback-is-in-progress

@krassowski
Copy link
Member Author

In a local test deployment what worked for me was running:

kubectl get secret -A | grep jupyterhub

This returns a list like

dev              nebari-jupyterhub-sftp                                              Opaque                                2      8d
dev              nebari-jupyterhub-ssh                                               Opaque                                1      8d
dev              sh.helm.release.v1.jupyterhub-dev.v1                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v2                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v3                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v4                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v5                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v6                                helm.sh/release.v1                    1      7d
dev              sh.helm.release.v1.jupyterhub-dev.v7                                helm.sh/release.v1                    1      1d

then find the the one with the greatest version (in this example sh.helm.release.v1.jupyterhub-dev.v7), then running:

kubectl delete secret sh.helm.release.v1.jupyterhub-dev.v7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo 📬
Development

No branches or pull requests

1 participant