<p>I was trying to uninstall a helm release in my AKS cluster using <code>helm uninstall RELEASE_NAME</code> but seems like it failed. The failure happened because for some reason all of the nodes in my cluster went in a not ready state when I used <code>helm uninstall</code>.</p>
<p>Since then, I got all the nodes to get back up and running and the cluster is functioning as it should. Now, when I do try <code>helm list</code>, I don't get to see this release present anymore, but doing a <code>helm list -a</code> shows me that the state of the release is still in <code>uninstalling</code> state. I have tried quite a few things, but it has been stuck there now for the last 3-4 days.</p>
<p>A few things that I tried was to use <code>helm uninstall RELEASE_NAME</code>, <code>helm delete --purge RELEASE_NAME</code> but these commands throw an error because the release is already in <code>uninstalling</code> state. I tried modifying the helm secrets in the cluster for this specific release but that didn't help either. <code>Helm3</code> is being used so it is not like I can restart the tiller pod to maybe stabilize this.</p>
<p>Does <code>Helm3</code> use some kind of a finalizer mechanism which can be modified to rectify this or
is there no alternate way in which I can perhaps try to delete this release? I want to use the same release name for the specific API in the future too.</p>
<p>Any help will be really appreciated.</p>

Saurav Saha
<p>Based on the discussion, the following steps resolve the issue.</p>
<pre><code>helm hist releasename
helm rollback releasename versionnumber-with-status-deployed
</code></pre>
<p>if this did not help, then delete secret for each version</p>
<pre><code>helm hist releasename
kubectl get secrets
k delete secrets sh.helm.release.v1.name.VERSION-N
</code></pre>
