vmwarefusion: kube-proxy configmap fail, Error configuring auth on host: OS type not recognized.

[tosbaha]

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

Please provide the following details:

Environment:

Minikube version (use minikube version):minikube version: v0.28.0

• OS: macOS High Sierra 10.13.5
• VM Driver :vmwarefusion
• ISO version :minikube-v0.28.0.iso
• Install tools:Homebrew

What happened:
Started minikube with minikube start --vm-driver=vmwarefusion

It hangs with

Starting cluster components...

then after a long time it shows

E0702 20:13:55.753952 6917 start.go:299] Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

I opened VMware Fusion and saw that minikube is running at login prompt. Next time I start minikube, it hangs at

Starting VM...
E0702 20:25:00.806264 7248 start.go:168] Error starting host: Temporary Error: Error configuring auth on host: OS type not recognized.
Retrying.

What you expected to happen:
Run minikube
How to reproduce it (as minimally and precisely as possible):
Install minikube v0.28.0 on High Sierra with homebrew. Try to start.
Output of minikube logs (if applicable):
minikube logs
F0702 20:26:10.695259 7322 logs.go:50] Error getting cluster bootstrapper: getting kubeadm bootstrapper: getting ssh client: Error dialing tcp via ssh client: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Anything else do we need to know:

[chainetix]

I get this on High Sierra when starting:

Alexanders-Air:docker alex$ minikube start --vm-driver=hyperkit
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0725 11:24:54.787814 81490 start.go:174] Error starting host: Error creating new host: dial tcp: missing address.

[podviaznikov]

Also have the same problem as @chainetix just by minikube start --vm-driver=hyperkit

[chainetix]

I fixed in the end by rebuilding or something

…

On Thu, 9 Aug 2018, 1:04 am Anton Podviaznikov, ***@***.***> wrote: Also have the same problem as @chainetix <https://github.com/chainetix> just by minikube start --vm-driver=hyperkit — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2955 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlopXUzaY045QykZ8yN5_kGFilCcnp0Rks5uO3yLgaJpZM4U_rig> .

[jhagege]

+1
@chainetix do you remember what were the steps you took to fix ?
Thanks.

[chainetix]

I think I downloaded the virtualization plugin whatever its called and built it from source. There are two main threads on this issue and it was a suggestion on one of them to do this. Unable to look into it as on a train at the sec.

…

On Sun, 19 Aug 2018, 12:34 pm jhagege, ***@***.***> wrote: +1 @chainetix <https://github.com/chainetix> do you remember what were the steps you took to fix ? Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2955 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlopXQSHE6uu63ivi1_sa0i-ROi8FJa8ks5uSU1TgaJpZM4U_rig> .

[tstromberg]

@tosbaha - do you mind testing with minikube 0.29.0 to see if it addresses your problem? It contains a vmwarefusion fixes: #3029

Thanks!

[tosbaha]

@tstromberg Sorry I no longer have that setup therefore I can't help it.

[fejta-bot]

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