Error restarting cluster: kube-proxy: server sent GOAWAY and closed the connection

[TheseusGrey]

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

Please provide the following details:

  Model Identifier:		MacBookPro14,3
  Processor Name:		Intel Core i7
  Processor Speed:		2.8 GHz
  Number of Processors:		1
  Total Number of Cores:	4
  L2 Cache (per Core):		256 KB
  L3 Cache:			6 MB
  Memory:			16 GB

Minikube version: v0.30.0

• OS macOS 10.13
• VM Driver Virtualbox
• ISO version minikube-v0.30.0.iso

What happened:
Attempted to start minikube, and was greeted with this:

E1121 17:13:38.093239    9334 status.go:85] Error cluster status: getting status: running command: sudo systemctl is-active kubelet
.: Process exited with status 3
Command failed with exit status 255: minikube status
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E1121 17:15:37.592969    9341 start.go:302] Error restarting cluster:  restarting kube-proxy: getting kube-proxy configmap: Get https://192.168.99.100:8443/api/v1/namespaces/kube-system/configmaps/kube-proxy: http2: server sent GOAWAY and closed the connection; LastStreamID=3, ErrCode=NO_ERROR, debug=""

Got a fresh ISO, then minikube did start after a couple of attempts, but when trying to start the dashboard, it gives a lot of 503 & 502 errors before giving up after a minute or so.

the GOAWAY response seems to have dissapeared for now but i'm still unable to access the dashboard and things have slowed down alot since i started having this issue, i'm unsure if this is significant or that other people may encounter it, but i wanted to make it known just incase.
How to reproduce it (as minimally and precisely as possible):
Unsure, seemed to happen somewhat randomly when i was restarting my cluster.

[TheseusGrey]

Just found a potentially similar issue: #3354

[tstromberg]

Thanks for the report! Next time you see this, do you mind running minikube logs and minikube status?

[tstromberg]

Also, what version of Virtualbox were you running? I saw some similar weirdness myself recently, but am on the 6.0.0 beta.

[TheseusGrey]

I'm currently running 5.2.22, I try to keep up to date with the latest stable release from brew.

[tstromberg]

We were seeing this across test environments, particularly with Kubernetes 1.12. Recent releases of minikube now default to v1.13, which seems to have addressed this issue. Hope this helps!

Thanks for the report!