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

hyperv: blocked on kube-proxy (solved by recreating virtual switch) #3765

Closed
BGaudreault-EDR opened this issue Feb 27, 2019 · 8 comments
Closed
Labels
co/hyperv HyperV related issues co/kube-proxy issues relating to kube-proxy in some way help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@BGaudreault-EDR
Copy link

BGaudreault-EDR commented Feb 27, 2019

On Windows 10 Ent 1709 (16299.371) with Docker Desktop v2.0.0.3 (31259) Build 8858db3 in a PowerShell Admin command window I type the command 'minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary vSwitch" (though I had to run the command twice to get this far!) and Minikube starts in Hyper-V, which I can see in the console and I can login, but PowerShell displays the following:

o minikube v0.34.1 on windows (amd64)
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
: Restarting existing hyperv VM for "minikube" ...
: Waiting for SSH access ...
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
: Re-using the currently running hyperv VM for "minikube" ...
: Waiting for SSH access ...
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
: Re-using the currently running hyperv VM for "minikube" ...
: Waiting for SSH access ...

  • "minikube" IP address is 10.24.8.149
  • Configuring Docker as the container runtime ...
  • Preparing Kubernetes environment ...
  • Pulling images required by Kubernetes v1.13.3 ...
    : Relaunching Kubernetes v1.13.3 using kubeadm ...
    : Waiting for kube-proxy to come back up ...
    ! Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

I then run 'minikube status' and get the following:

host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at 10.24.8.149

I then run 'kubectl get pods -n kube-system' and get the following:

NAME READY STATUS RESTARTS AGE
etcd-minikube 1/1 Running 0 27m
kube-addon-manager-minikube 1/1 Running 2 26d
kube-apiserver-minikube 1/1 Running 0 27m
kube-controller-manager-minikube 1/1 Running 0 27m
kube-scheduler-minikube 1/1 Running 1 1h
storage-provisioner 0/1 CrashLoopBackOff 139 26d

Also I pre-configured Hyper-V with the following configurations I read were recommended for Windows:

• Hyper-V Manager > select local computer > Virtual Switch Manager... (right panel) > Create Virtual Switch (New virtual network switch, External) > Name: "Primary vSwitch"

• To address a bug in minikube for Windows (#2326) I turned off Dynamic Memory for minikube VM: Rrun 'minikube stop' first > Hyper-V Manager: right-click minikube VM > Settings... > Memory > UNcheck Enable Dynamic Memory > APPLY > optionally close Hyper-V manager.

@tstromberg tstromberg changed the title Windows 10 Error Restarting Cluster hyperv: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition Mar 8, 2019
@tstromberg tstromberg added co/hyperv HyperV related issues co/kube-proxy issues relating to kube-proxy in some way kind/bug Categorizes issue or PR as related to a bug. labels Mar 8, 2019
@tstromberg
Copy link
Contributor

tstromberg commented Mar 8, 2019

I believe this should be addressed by minikube v0.35.0 - we no longer block on the kube-proxy in the same way. That said, you may run into some other issues.

I encourage you to run minikube delete first to remove the previous half-setup state. Thanks! I look forward to hearing if the error message changes or if it gets through properly.

@fracmak
Copy link

fracmak commented Mar 8, 2019

I found minikube delete didn't solve my problem. I had to delete the network interface for virtualbox and let minikube recreate it before everything went back to normal

@tstromberg
Copy link
Contributor

OK. Thanks for the update! What did minikube v0.35.0 say before deleting the network interface?

@tstromberg tstromberg added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 8, 2019
@fracmak
Copy link

fracmak commented Mar 8, 2019

same error message above in this issue. I could ssh in and see that kube-proxy was indeed running, but whatever reason it wouldn't get past that step until I deleted the network interface

@tstromberg tstromberg added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it. labels Mar 8, 2019
@tstromberg tstromberg changed the title hyperv: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition hyperv: blocked on kube-proxy (solved by recreating virtual switch) Mar 8, 2019
@tstromberg
Copy link
Contributor

tstromberg commented Mar 8, 2019

Thanks for the additional info!

@Ben197
Copy link

Ben197 commented Apr 5, 2019

Minikube in Windows Prof is still not working, I can't disable the dynamic ram like adviced because the kube is running. I going to try it on my LInux system. Windows never works with open source tooling.
PowerShellMiniKube

@tstromberg
Copy link
Contributor

I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube, and if the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience!

@Ben197
Copy link

Ben197 commented May 24, 2019

I have minikube successfully running on my Linux Ubuntu system.
Thx for your support anyway!!
Maybe I try it later again via the hyper-V driver with minikube v1.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/hyperv HyperV related issues co/kube-proxy issues relating to kube-proxy in some way help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

4 participants