helm upgrade --install throws incorrect error.

Created on 2 Nov 2018  路  1Comment  路  Source: helm/helm

I was trying to deploy a new release using the Helm upgrade --install command.

When I executed the command first

helm upgrade --install gautam-server-test-987 --values test-values.yaml . --debug
[debug] Created tunnel using local port: '42349'
[debug] SERVER: "127.0.0.1:42349"
Release "gautam-server-test-987" does not exist. Installing it now.
[debug] CHART PATH: /home/gamoulik_1/skyman-codebase/SkymanDocker/kubernetes/helm/mtleaf
Error: release gautam-server-test-987 failed: configmaps "myapp-config-gautam-server-test-987" already exists.

[Note: This is an incorrect error, the config map just can't exist because I have never installed this before.]
However, though the install fails I can see the config maps now with the same name and I delete the config maps using the kubectl command and execute the command one more time

helm upgrade --install gautam-server-test-987 --values test-values.yaml . --debug

Now, it says

[debug] Created tunnel using local port: '41683'
[debug] SERVER: "127.0.0.1:41683"
WARNING: Namespace doesn't match with previous. Release will be deployed to default
Error: UPGRADE FAILED: "gautam-server-test-987" has no deployed releases.

helm ls | grep gautam-server-test-987 shows an entry and status as failed.

Please note that, this command has worked before without any trouble, not sure of why is it stopped working suddenly.
Also, is there a way to check the Helm upgrade --install command log ? as in, to find out what actually went wrong, I was using --debug to see the verbose output of each and every steps but the it fails.

Output of helm version:

Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:59:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:52:38Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

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

_Edited to add code blocks for readability_

bug questiosupport

Most helpful comment

We have the same issue. As workaround - you can add the --force flag to helm upgrade command.
Or use helm delete with --purge and after install the chart from scratch.

>All comments

We have the same issue. As workaround - you can add the --force flag to helm upgrade command.
Or use helm delete with --purge and after install the chart from scratch.

Was this page helpful?
0 / 5 - 0 ratings