running helm reset --force after uninstalling helm hangs

[janitha09]

$ helm init --service-account tiller --history-max 200
$HELM_HOME has been configured at /home/ubuntu/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!

$ kubectl get deployments --all-namespaces
NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
default       hello-node                1/1     1            1           20h
kube-system   calico-kube-controllers   1/1     1            1           23h
kube-system   coredns                   2/2     2            2           23h
kube-system   tiller-deploy             1/1     1            1           110s

then uninstall helm

$ helm reset
Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.
$ helm reset
Error: forwarding ports: error upgrading connection: unable to upgrade connection: pod not found ("tiller-deploy-876ff889-6jvsc_kube-system")

try a force (did it by accident)

$ helm reset --force

this hangs and does not return Ctrl-C to get out after about a minute
adding the --debug flag doesn't provide additional information

Output of helm version:

$ helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Output of kubectl version:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

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

$ uname -a
Linux <hostname> 4.15.0-1032-aws #34-Ubuntu SMP Thu Jan 17 15:18:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[hickeyma]

I was able to reproduce this as follows:

$ helm reset
Tiller (the Helm server-side component) has been uninstalled from your Kubernetes Cluster.

$ helm reset
Error: could not find tiller

It will then hang when call it is called with --force flag after Tiller has been uninstalled:

$ helm reset --force
[.......]

@janitha09 Thanks for finding this bug.