Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2.4.0 Not using k8s config #2376

Closed
dkoshkin opened this issue May 3, 2017 · 6 comments
Closed

V2.4.0 Not using k8s config #2376

dkoshkin opened this issue May 3, 2017 · 6 comments
Milestone

Comments

@dkoshkin
Copy link

dkoshkin commented May 3, 2017

Ran ./helm init

➜  out git:(helm) ✗ kubectl get nodes
NAME        STATUS                     AGE       VERSION
master001   Ready,SchedulingDisabled   17m       v1.6.2
worker001   Ready                      17m       v1.6.2
worker002   Ready                      17m       v1.6.2
➜  out git:(helm) ✗ export KUBECONFIG=~/.kube/config
➜  out git:(helm) ✗ stat ~/.kube/config
16777220 22173086 -rw-r--r-- 1 dkoshkin (1535981906 0 6228 "May  2 20:42:16 2017" "May  2 20:36:45 2017" "May  2 20:36:45 2017" "May  2 16:12:41 2017" 4096 16 0 /Users/dkoshkin/.kube/config
➜  out git:(helm) ✗ ./helm version
Client: &version.Version{SemVer:"v2.4.0", GitCommit:"1ec2c04be8d4d69c15b85df97394bfa2f5919f03", GitTreeState:"clean"}
^C
➜  out git:(helm) ✗ ./helm init
$HELM_HOME has been configured at /Users/dkoshkin/.helm.
Error: error installing: Post http://localhost:8080/apis/extensions/v1beta1/namespaces/kube-system/deployments: dial tcp [::1]:8080: getsockopt: connection refused
➜  out git:(helm) ✗

Expected to run successfully, the cluster is not running locally but looks like Helm is not picking up the kube config file. The same cluster setup works fine with v2.3.1

@rodcloutier
Copy link
Contributor

After a git bisect the following commit 4d8f23e introduced the break

@yuvipanda
Copy link
Contributor

A strace tells me it does open and read $HOME/.kube/config, but still tries to hit localhost.

@yuvipanda
Copy link
Contributor

This isn't just helm init - all helm commands fail with similar reason (even when there's a tiller running already)

@rodcloutier
Copy link
Contributor

Changing the github.com/imdario/mergo dependency to the previous version fixes the problem.

darccio/mergo@6633656 is fine
darccio/mergo@3e95a51 is breaks

@rodcloutier
Copy link
Contributor

Kubernetes is also using mergo Maybe a clash in versions?

@rodcloutier
Copy link
Contributor

rodcloutier commented May 3, 2017

I suggest to pin the version of mergo to a known working version for both sprig and Kubernetes. Would this be fine?

adamreese pushed a commit to adamreese/helm that referenced this issue May 3, 2017
    Reverted the version of mergo to a version that was known to work
    with both kubernetes and sprig.

    Closes helm#2376
@michelleN michelleN added this to the 2.4.1 - Bugs milestone May 3, 2017
opencontrail-ci-admin pushed a commit to Juniper/contrail-docker that referenced this issue Jul 19, 2017
With helm v2.4.0 we were hitting issue
helm/helm#2376. Added RBAC role for tiller pod
manifest and changed the tiller version to stable v2.4.2. Fixed contrail
vrouter issues on centos host operating system.

Change-Id: I142f1e14558daf4a2ca455aa85ca2fd6c781c885
Partial-Bug: #1693646
Implements: blueprint contrail-helm-charts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants