-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
hyperv restart: waiting for component=kube-apiserver: timed out waiting for the condition #3836
Comments
Thank you for the bug report! I'm sorry to hear that minikube failed in this environment. Do you mind providing the output of:
and
It's possible that creating a new cluster or running Thank you! |
I did a verbose while restarting and got the following information
status:
this is the output of the logs
|
I tried using both an internal switch and an external switch created in Hyper V but it is not working |
I am using a Windows 10 machine, minikube version v.35.0 |
So, the apiserver crashed. Can you drag & drop the output of the
This may be related to #1766 - where strange things happen when dynamic memory is enabled in HyperV. If you get a chance, do you mind trying to start the https://www.veeam.com/blog/hyper-v-dynamic-memory-managing-vm-ram.html I don't have a HyperV host yet, otherwise I would give better directions. Please let me know if this helps. Thank you again for the detailed information! |
Same problem with the latest version on Mac. I have deleted everything, including ~/.minikube and retried from scratch. I am getting consistent results:
I have noticed that minikube VM has two network interfaces. Is that normal? |
Hi. I'm experiencing the same issue on Mac Mohave: $ minikube start 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: $minikube status $ minikube logs ==> dmesg <== ==> kernel <== ==> kube-addon-manager <== ==> kube-apiserver <== ==> kube-proxy <== ==> kube-scheduler <== ==> kubelet <== ==> storage-provisioner <== |
Regrettably, 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 suspect this was due to #1766 - but there are other possibilities as well. If you run into this issue with minikube v1.0.1+ on hyperv, please feel free to add to this issue. |
I have installed minikube for windows and made necessary changes for Hyper V but still I get this error when I try to restart (I did delete and try again as well but no luck)
The text was updated successfully, but these errors were encountered: