# Helm upgrade failed another operation is in progress **URL:** \ **Category:** General\ **Created:** [April 30, 2024, 9:57am UTC](https://forums.suse.com/t/helm-upgrade-failed-another-operation-is-in-progress/43061 "2024-04-30T09:57:43Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Rafael](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Rafael](https://forums.suse.com/u/Rafael)\ **Post date:** [April 30, 2024, 9:57am UTC](https://forums.suse.com/t/helm-upgrade-failed-another-operation-is-in-progress/43061/1 "2024-04-30T09:57:43Z")
Some time ago I did an upgrade to rancher v.2.8.2 which at first sight happened successfully. But now that I want to do an upgrade to v2.8.3 helm gives the following error. rancher Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress I did some digging around and came with the following information. helm history -n cattle-system rancher REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 1 Mon Nov 27 13:25:44 2023 deployed rancher-2.7.9 v2.7.9 Install complete 2 Thu Mar 14 13:30:54 2024 pending-upgrade rancher-2.8.2 v2.8.2 Preparing upgrade helm ls -a -n cattle-system | NAME | NAMESPACE | REVISION | UPDATED | STATUS | CHART | APP VERSION | | --- | --- | --- | --- | --- | --- | --- | | rancher | cattle-system | 2 | 2024-03-14 13:30:54.905346542 +0100 CET | pending-upgrade | rancher-2.8.2 | v2.8.2 | | rancher-webhook | cattle-system | 2 | 2024-03-14 12:34:35.935552673 +0000 UTC | deployed | rancher-webhook-103.0.1+up0.4.2 | 0.4.2 | As you can see the current version i’m using for some time now v2.8.2 is still in “pending upgrade” kubectl get secret -n cattle-system -l status=pending-upgrade NAME TYPE DATA AGE sh.helm.release.v1.rancher.v2 helm.sh/release.v1 1 46d Any idea how to solve this? I also rather not do a rollback if possible since v2.8.2 is working fine for the rest. ---
**Author:** ![Rafael](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Rafael](https://forums.suse.com/u/Rafael)\ **Post date:** [May 7, 2024, 9:21am UTC](https://forums.suse.com/t/helm-upgrade-failed-another-operation-is-in-progress/43061/2 "2024-05-07T09:21:44Z")
I deleted the secret wich also means helm has no idea about revision 2 anymore but this way I was able to upgrade my cluster. Not sure if this was the right way to do it but because these issues aren’t really documented anywhere I gave it a shot and so far it works.