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

using a profile with hyperkit hangs: failed to get node info: node "minikube" not found #3103

Closed
gintautassulskus opened this issue Aug 30, 2018 · 5 comments
Labels
area/profiles issues related to profile handling co/hyperkit Hyperkit related issues ev/apiserver-refused failures due to the master on 8443 returning "Connection Refused" ev/hung-start kind/bug Categorizes issue or PR as related to a bug. triage/obsolete Bugs that no longer occur in the latest stable release

Comments

@gintautassulskus
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Please provide the following details:

Environment:

  • Minikube version: v0.28.2
  • OS: macOS 10.13.6
  • VM Driver: hyperkit
  • ISO version: minikube-v0.28.1.iso

What happened:
As the title says, minikube with --vm-driver hyperkit and non-default profile won't start. The initialisation process gets stuck at:

Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...

What you expected to happen:
Expected a successful initialisation.

How to reproduce it (as minimally and precisely as possible):
minikube start --profile test.minikube.local --vm-driver hyperkit

Output of minikube logs (if applicable):

Aug 30 22:37:25 test.minikube.local kubelet[2389]: E0830 22:37:25.248823    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:26 test.minikube.local kubelet[2389]: E0830 22:37:26.097586    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:26 test.minikube.local kubelet[2389]: E0830 22:37:26.097603    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:26 test.minikube.local kubelet[2389]: E0830 22:37:26.251971    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:27 test.minikube.local kubelet[2389]: E0830 22:37:27.099839    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:27 test.minikube.local kubelet[2389]: E0830 22:37:27.100257    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:27 test.minikube.local kubelet[2389]: E0830 22:37:27.256195    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:28 test.minikube.local kubelet[2389]: E0830 22:37:28.102893    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:28 test.minikube.local kubelet[2389]: E0830 22:37:28.102945    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:28 test.minikube.local kubelet[2389]: E0830 22:37:28.260646    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:29 test.minikube.local kubelet[2389]: E0830 22:37:29.107202    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:29 test.minikube.local kubelet[2389]: E0830 22:37:29.107875    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:29 test.minikube.local kubelet[2389]: E0830 22:37:29.261553    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:30 test.minikube.local kubelet[2389]: E0830 22:37:30.108172    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:30 test.minikube.local kubelet[2389]: E0830 22:37:30.109222    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:30 test.minikube.local kubelet[2389]: E0830 22:37:30.262481    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:30 test.minikube.local kubelet[2389]: I0830 22:37:30.401788    2389 kubelet_node_status.go:271] Setting node annotation to enable volume controller attach/detach
Aug 30 22:37:31 test.minikube.local kubelet[2389]: E0830 22:37:31.113505    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:451: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:31 test.minikube.local kubelet[2389]: E0830 22:37:31.113505    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:460: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:31 test.minikube.local kubelet[2389]: E0830 22:37:31.263921    2389 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8443: getsockopt: connection refused
Aug 30 22:37:31 test.minikube.local kubelet[2389]: E0830 22:37:31.561763    2389 eviction_manager.go:246] eviction manager: failed to get get summary stats: failed to get node info: node "minikube" not found

No other output really.

@tstromberg tstromberg changed the title Minikube with --vm-driver hyperkit and non-default profile won't start using a profile with hyperkit hangs: failed to get node info: node "minikube" not found Sep 18, 2018
@tstromberg
Copy link
Contributor

This sounds like it may have similar root causes to #2574, but on HyperV. Won't mark as a dupe because I'm not entirely confident just yet.

@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. ev/apiserver-refused failures due to the master on 8443 returning "Connection Refused" labels Sep 19, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 17, 2019
@tstromberg tstromberg added area/profiles issues related to profile handling and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/macos labels Jan 23, 2019
@tstromberg
Copy link
Contributor

I'm curious - has anyone tested this with minikube v0.33? It seems to have addressed other profile quirks.

@tstromberg
Copy link
Contributor

Tested with v0.33.1, and this bug appears to be obsolete. Thank you for reporting it!

@tstromberg tstromberg added the triage/obsolete Bugs that no longer occur in the latest stable release label Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/profiles issues related to profile handling co/hyperkit Hyperkit related issues ev/apiserver-refused failures due to the master on 8443 returning "Connection Refused" ev/hung-start kind/bug Categorizes issue or PR as related to a bug. triage/obsolete Bugs that no longer occur in the latest stable release
Projects
None yet
Development

No branches or pull requests

4 participants