Helm 3 upgrade --install faild has no deployed release

[HamzaZo]

I'm using Helm 3 to install my chart using the following command :

helm upgrade --install project-x --wait --timeout 400s project-x/

I got Error: UPGRADE FAILED: "project-x" has no deployed releases
and the output of helm ls as follows:

helm ls
NAME     NAMESPACE    REVISION	UPDATED     STATUS     CHART       APP VERSION                   
project-x	app-dev                1         	2019-12-17    failed        project-x	  0.0.1

Output of helm version: v3.0.1

Output of kubectl version: v1.14.8-gke.17

Cloud Provider/Platform (AKS, GKE, Minikube etc.): GKE

Does anyone has an idea ?
Thanks

[phumberdroz]

I encountered something similar looking at this it seems like it is a first install of a chart.
You can simply helm delete project-x and then install again.

[HamzaZo]

@phumberdroz in CI/CD we can't simply delete the chart

[phumberdroz]

Right but this is b/c the first release failed right?

You can read more about why that is here: #3353

[HamzaZo]

@phumberdroz Yes, the first release failed

Is there any future work to change the logic when the initial release ends up in a failed state ?

cc @bacongobbler

[bacongobbler]

closing as a duplicate of #5595.

[ryudice]

I'm having this exact issue, but in my case I have no charts installed, the output of helm ls is empty yet I'm getting this error. Any ideas?

[medavisjr]

I'm having this exact issue, but in my case I have no charts installed, the output of helm ls is empty yet I'm getting this error. Any ideas?

@ryudice My guess would be that your kubeconfig is pointed at another namespace, such that when you issue "helm ls" you see no deployments. But when you issue your helm upgrade command, you're providing the namespace where the release is deployed.

[abdennour]

same issue as well as upgrading from helm 2 to helm 3.
Error: UPGRADE FAILED: "company-services-development" has no deployed releases
Should we install it from scartch using helm install instead of helm upgrade ?

[mcbenjemaa]

The problem was, that the previous helm chart stuck on uninstalling state for any reason and you can find it via helm ls --all-namespaces -a | grep whatever
Deleting the old release fixes the issue.

[vinayGudi]

@medmedchiheb yes deleting the release will work but it is not always the good idea.
in our case we have large dbs running....if we delete the release every time we encounter this problem then always we lose data in pv and need to restore the latest snapshot version :(