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

minikube node start logs unexpected first step #9830

Closed
lingsamuel opened this issue Dec 3, 2020 · 0 comments · Fixed by #9832
Closed

minikube node start logs unexpected first step #9830

lingsamuel opened this issue Dec 3, 2020 · 0 comments · Fixed by #9832
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@lingsamuel
Copy link
Contributor

Steps to reproduce the issue:

  1. minikube start
  2. minikube node stop xxx
  3. minikube node start xxx

Full output of failed command:
No a failure, but strange (network options removed):

E1203 11:01:03.130387 1503395 register.go:125] unexpected first step: ""
👍  Starting node minikube-m02 in cluster minikube
🔄  Restarting existing kvm2 VM for "minikube-m02" ...
❗  This VM is having trouble accessing https://k8s.gcr.io
💡  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
E1203 11:01:14.403140 1503395 register.go:125] unexpected first step: ""
🐳  Preparing Kubernetes v1.19.3 on Docker 19.03.12 ...
    ▪ env NO_PROXY=localhost,127.0.0.0/8,::1,192.168.0.0/16,zju.edu.cn,tsinghua.edu.cn,ustc.edu.cn
E1203 11:01:55.040378 1503395 register.go:125] unexpected first step: ""
🔎  Verifying Kubernetes components...
😄  Successfully started node minikube-m02!
@medyagh medyagh added the kind/bug Categorizes issue or PR as related to a bug. label Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants