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.

Sign up for GitHub

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

Jump to bottom

minikube ip Exiting due to GUEST_NODE_RETRIEVE: Could not find node #10322

Closed
hayorov opened this issue Jan 31, 2021 · 6 comments
Closed

minikube ip Exiting due to GUEST_NODE_RETRIEVE: Could not find node #10322

hayorov opened this issue Jan 31, 2021 · 6 comments
Labels
co/hyperkit Hyperkit related issues kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. long-term-support Long-term support issues that can't be fixed in code

Comments

@hayorov
Copy link

hayorov commented Jan 31, 2021

Steps to reproduce the issue:

  1. brew install [email protected]
  2. minukube start
  3. minikube ip

Full output of failed command:
❯ minikube ip --v=8 --alsologtostderr
I0131 15:20:36.463309 16328 out.go:229] Setting OutFile to fd 1 ...
I0131 15:20:36.463716 16328 out.go:281] isatty.IsTerminal(1) = true
I0131 15:20:36.463723 16328 out.go:242] Setting ErrFile to fd 2...
I0131 15:20:36.463728 16328 out.go:281] isatty.IsTerminal(2) = true
I0131 15:20:36.463806 16328 root.go:291] Updating PATH: /Users/alexk/.minikube/bin
I0131 15:20:36.464359 16328 mustload.go:66] Loading cluster: minikube
I0131 15:20:36.465485 16328 main.go:119] libmachine: Found binary path at /Users/alexk/.minikube/bin/docker-machine-driver-hyperkit
I0131 15:20:36.465538 16328 main.go:119] libmachine: Launching plugin server for driver hyperkit
I0131 15:20:36.475493 16328 main.go:119] libmachine: Plugin server listening at address 127.0.0.1:53014
I0131 15:20:36.476038 16328 main.go:119] libmachine: () Calling .GetVersion
I0131 15:20:36.476924 16328 main.go:119] libmachine: Using API Version 1
I0131 15:20:36.476941 16328 main.go:119] libmachine: () Calling .SetConfigRaw
I0131 15:20:36.477191 16328 main.go:119] libmachine: () Calling .GetMachineName
I0131 15:20:36.477317 16328 main.go:119] libmachine: (minikube) Calling .GetState
I0131 15:20:36.477438 16328 main.go:119] libmachine: (minikube) DBG | exe=/Users/alexk/.minikube/bin/docker-machine-driver-hyperkit uid=0
I0131 15:20:36.477701 16328 main.go:119] libmachine: (minikube) DBG | hyperkit pid from json: 15777
I0131 15:20:36.479541 16328 host.go:66] Checking if "minikube" exists ...
I0131 15:20:36.479812 16328 main.go:119] libmachine: Found binary path at /Users/alexk/.minikube/bin/docker-machine-driver-hyperkit
I0131 15:20:36.479844 16328 main.go:119] libmachine: Launching plugin server for driver hyperkit
I0131 15:20:36.488713 16328 main.go:119] libmachine: Plugin server listening at address 127.0.0.1:53020
I0131 15:20:36.489104 16328 main.go:119] libmachine: () Calling .GetVersion
I0131 15:20:36.489532 16328 main.go:119] libmachine: Using API Version 1
I0131 15:20:36.489547 16328 main.go:119] libmachine: () Calling .SetConfigRaw
I0131 15:20:36.489866 16328 main.go:119] libmachine: () Calling .GetMachineName
I0131 15:20:36.489993 16328 main.go:119] libmachine: (minikube) Calling .DriverName
I0131 15:20:36.513440 16328 out.go:119]

W0131 15:20:36.513594 16328 out.go:181] ❌ Exiting due to GUEST_NODE_RETRIEVE: Could not find node
❌ Exiting due to GUEST_NODE_RETRIEVE: Could not find node
W0131 15:20:36.515643 16328 out.go:181]

W0131 15:20:36.515684 16328 out.go:181] 😿 If the above advice does not help, please let us know:
😿 If the above advice does not help, please let us know:
W0131 15:20:36.515721 16328 out.go:181] 👉 https://github.com/kubernetes/minikube/issues/new/choose
👉 https://github.com/kubernetes/minikube/issues/new/choose
I0131 15:20:36.584507 16328 out.go:119]

Full output of minikube start command used, if not already included:
❯ minikube start
😄 minikube v1.17.1 on Darwin 11.1
🆕 Kubernetes 1.20.2 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.20.2
✨ Using the hyperkit driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing hyperkit VM for "minikube" ...
🐳 Preparing Kubernetes v1.19.0 on Docker 19.03.6 ...
🔎 Verifying Kubernetes components...
🌟 Enabled addons: storage-provisioner, default-storageclass, dashboard
🏄 Done! kubectl is now configured to use "minikube" cluster and "" namespace by default

** Environment **
❯ uname -a
Darwin alexmbp 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64

Meanwhile, IP returns when the -n argument is defined
❯ k get nodes
NAME STATUS ROLES AGE VERSION
minikube Ready master 2m10s v1.19.0

❯ minikube ip -n minikube --v=8 --alsologtostderr
I0131 15:28:11.675406 17047 out.go:229] Setting OutFile to fd 1 ...
I0131 15:28:11.675947 17047 out.go:281] isatty.IsTerminal(1) = true
I0131 15:28:11.675957 17047 out.go:242] Setting ErrFile to fd 2...
I0131 15:28:11.675964 17047 out.go:281] isatty.IsTerminal(2) = true
I0131 15:28:11.676064 17047 root.go:291] Updating PATH: /Users/alexk/.minikube/bin
I0131 15:28:11.676604 17047 mustload.go:66] Loading cluster: minikube
I0131 15:28:11.677538 17047 main.go:119] libmachine: Found binary path at /Users/alexk/.minikube/bin/docker-machine-driver-hyperkit
I0131 15:28:11.677602 17047 main.go:119] libmachine: Launching plugin server for driver hyperkit
I0131 15:28:11.688985 17047 main.go:119] libmachine: Plugin server listening at address 127.0.0.1:53289
I0131 15:28:11.689705 17047 main.go:119] libmachine: () Calling .GetVersion
I0131 15:28:11.690506 17047 main.go:119] libmachine: Using API Version 1
I0131 15:28:11.690522 17047 main.go:119] libmachine: () Calling .SetConfigRaw
I0131 15:28:11.690864 17047 main.go:119] libmachine: () Calling .GetMachineName
I0131 15:28:11.691021 17047 main.go:119] libmachine: (minikube) Calling .GetState
I0131 15:28:11.691171 17047 main.go:119] libmachine: (minikube) DBG | exe=/Users/alexk/.minikube/bin/docker-machine-driver-hyperkit uid=0
I0131 15:28:11.691726 17047 main.go:119] libmachine: (minikube) DBG | hyperkit pid from json: 16705
I0131 15:28:11.693466 17047 host.go:66] Checking if "minikube" exists ...
I0131 15:28:11.693832 17047 main.go:119] libmachine: Found binary path at /Users/alexk/.minikube/bin/docker-machine-driver-hyperkit
I0131 15:28:11.693863 17047 main.go:119] libmachine: Launching plugin server for driver hyperkit
I0131 15:28:11.704383 17047 main.go:119] libmachine: Plugin server listening at address 127.0.0.1:53295
I0131 15:28:11.704877 17047 main.go:119] libmachine: () Calling .GetVersion
I0131 15:28:11.705465 17047 main.go:119] libmachine: Using API Version 1
I0131 15:28:11.705481 17047 main.go:119] libmachine: () Calling .SetConfigRaw
I0131 15:28:11.705951 17047 main.go:119] libmachine: () Calling .GetMachineName
I0131 15:28:11.706155 17047 main.go:119] libmachine: (minikube) Calling .DriverName
I0131 15:28:11.746611 17047 out.go:119] 192.168.64.3
192.168.64.3

Probably affected by multi-instance support, the latest touch was here #9873
@RA489
Copy link

RA489 commented Feb 4, 2021

/kind support

@k8s-ci-robot k8s-ci-robot added the kind/support Categorizes issue or PR as a support question. label Feb 4, 2021
@RA489 RA489 added the co/hyperkit Hyperkit related issues label Feb 4, 2021
@netrebel
Copy link

netrebel commented Mar 1, 2021

I started getting this error too. Workaround is minikube ip -n minikube, see below:

➜  kubernetes git:(master) ✗ minikube version
minikube version: v1.17.1
commit: 043bdca07e54ab6e4fc0457e3064048f34133d7e

➜  kubernetes git:(master) ✗ minikube ip

❌  Exiting due to GUEST_NODE_RETRIEVE: Could not find node

😿  If the above advice does not help, please let us know:
👉  https://github.com/kubernetes/minikube/issues/new/choose

➜  kubernetes git:(master) ✗ minikube node list
minikube	192.168.64.13

➜  kubernetes git:(master) ✗ minikube ip -n minikube
192.168.64.13

@spowelljr
Copy link
Member

spowelljr commented Mar 31, 2021 •
edited
Loading

@hayorov In your issue you're restarting an existing cluster, I'm curious if you delete and re-start again if the issue is solved.

There could also possibly be a fix in v1.18.1 if you could download the latest version, thanks.

@spowelljr spowelljr added long-term-support Long-term support issues that can't be fixed in code and removed triage/long-term-support labels May 19, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Aug 17, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Sep 16, 2021
@spowelljr
Copy link
Member

Hi @hayorov, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/hyperkit Hyperkit related issues kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. long-term-support Long-term support issues that can't be fixed in code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@netrebel @hayorov @k8s-ci-robot @RA489 @spowelljr @k8s-triage-robot