VM: Error restarting cluster: waiting for apiserver: apiserver process never appeared

[zzzhy]

The exact command to reproduce the issue:
minikube start --cache-images --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --cpus 4 --memory 12680

The full output of the command that failed:

💣 Error restarting cluster: waiting for apiserver: apiserver process never appeared
Problems detected in kube-addon-manager ["792bb2ae3606"]:
error: error pruning namespaced object /v1, Kind=Service: Get https://localhost:8443/api/v1/namespaces/kube-system/services?labelSelector=kubernetes.io%2Fcluster-service%21%3Dtrue%2Caddonmanager.kubernetes.io%2Fmode%3DReconcile: dial tcp 127.0.0.1:8443: connect: connection refused

The output of the minikube logs command:

😄 minikube v1.5.2 on Darwin 10.15.1
✅ Using image repository registry.cn-hangzhou.aliyuncs.com/google_containers
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
🏃 Using the running virtualbox "minikube" VM ...
⌛ Waiting for the host to be provisioned ...
🐳 Preparing Kubernetes v1.16.2 on Docker '18.09.9' ...
🔄 Relaunching Kubernetes using kubeadm ...

💣 Error restarting cluster: waiting for apiserver: apiserver process never appeared

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
❌ Problems detected in kube-addon-manager ["792bb2ae3606"]:
error: error pruning namespaced object /v1, Kind=Service: Get https://localhost:8443/api/v1/namespaces/kube-system/services?labelSelector=kubernetes.io%2Fcluster-service%21%3Dtrue%2Caddonmanager.kubernetes.io%2Fmode%3DReconcile: dial tcp 127.0.0.1:8443: connect: connection refused

The operating system version:
Mac Catalina 10.15.1 (19B88)

[zzzhy]

when recreate minikube vm, it turns out working fine !

[priyawadhwa]

hey @zzzhy, thanks for opening this! looks like the apiserver didn't come up. I'll go ahead and close this issue since it seems restart solved your issue.

[tstromberg]

Possibly related PR: #5916

If it happens again, please share the output of minikube logs. Thanks!

[tstromberg]

I believe we fixed this with #5916 - the fix is included with minikube v1.6.

If you run into this issue and are not specifically using the 'none' driver, please try with the latest release of minikube, and add a comment saying /reopen if it's still an issue.

If you are using --vm-driver=none, it's likely something entirely different, so please open a new issue.