Subsequent error on minikube restart:
minikube v1.4.0 on Darwin 10.14.3
๐ก Tip: Use 'minikube start -p <name>' 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.0 on Docker 18.09.8 ...
๐ Relaunching Kubernetes using kubeadm ...
E0920 14:15:18.905571 77264 kubeadm.go:415] failed to create compat symlinks: cmd failed: sudo ln -s /data/minikube /var/lib/minikube/etcd
ln: failed to create symbolic link '/var/lib/minikube/etcd/minikube': File exists
: Process exited with status 1
_Originally posted by @vsethi in https://github.com/kubernetes/minikube/issues/5415#issuecomment-533848677_
My suspicion is that this regression may be tied only to restart on older ISO's.
Hit this issue today. Let me know if there is information that would be helpful to include.
Hit this issue today. Let me know if there is information that would be helpful to include.
@seancarroll @dbamaster I am curious, does this issue happen consistently or only happens sometimes ?
if this issue is still happening for you, I wonder if deleting the ISO cache would solve your problem ?
rm ~/.minikube/cache/iso/*
or if minikube delete and starting it fresh would solve the problem ?
Since I first encountered it its been consistent. I deleted minikube but didnt help so I tried to reinstalled virtualbox as well but that too hasnt resolved the issue for me.
Interesting. As far as I knew, this issue should only happen on existing VM's with older ISO's, so minikube delete should have solved the issue.
Hit this issue today. Let me know if there is information that would be helpful to include.
@seancarroll @dbamaster I am curious, does this issue happen consistently or only happens sometimes ?
if this issue is still happening for you, I wonder if deleting the ISO cache would solve your problem ?
rm ~/.minikube/cache/iso/*or if
minikube deleteand starting it fresh would solve the problem ?
It happened after the last update.
Deleting minikube is not an option for me. I have a few deployments there, unfortunately I didn't save the actual file :(
got error
๐ฃ Error restarting cluster: addon phase: command failed: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init phase addon all --config /var/tmp/minikube/kubeadm.yaml
stdout:
stderr: error execution phase addon/coredns: unable to fetch CoreDNS current installed version and ConfigMap.: multiple DNS addon deployments found: [{{ } {coredns kube-system /apis/apps/v1/namespaces/kube-system/deployments/coredns c0600e1f-a2ac-41ad-9fd3-2c40d6e8d0d9 2098 1 2019-10-26 13:15:06 +0000 UTC
To see the stack trace of this error execute with --v=5 or higher
: Process exited with status 1
rm ~/.minikube/cache/iso/*
This didnt helped in my case. However minikube delete did work. :tada:
Deleting minikube is not an option for me. I have a few deployments there, unfortunately I didn't save the actual file :(
@dbamaster what about temporary downgrading and doing: kubectl get deployment FOO -o yaml > my-deployment-foo.yml to save your deployments
rm ~/.minikube/cache/iso/*
This didnt helped in my case. However
minikube deletedid work. ๐Deleting minikube is not an option for me. I have a few deployments there, unfortunately I didn't save the actual file :(
@dbamaster what about temporary downgrading and doing:
kubectl get deployment FOO -o yaml > my-deployment-foo.ymlto save your deployments
I did that thank you, I will try to re-install Minikube and see how it goes.
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
@seancarroll @WtfJoke @dbamaster @tstromberg is this still an issue ? I have not see this issue in a while, could it have been fixed by the latest version ?
@medyagh I only experienced this error once and since then I havent worked much with k8/minikube anymore. So I cant tell if its really fixed, but will let you know if I experience it again
@seancarroll @WtfJoke @dbamaster @tstromberg is this still an issue ? I have not see this issue in a while, could it have been fixed by the latest version ?
Hey @medyagh thanks for the follow-up, I will check and update.
It is a long time since I uninstalled minikube from my laptop.
Regards,
FWIW, I had this problem today and minikube delete solved it for me.
I had this problem after upgrading mac OS to catalina, andminikube deletedid solve the issue
Most helpful comment
@seancarroll @dbamaster I am curious, does this issue happen consistently or only happens sometimes ?
if this issue is still happening for you, I wonder if deleting the ISO cache would solve your problem ?
rm ~/.minikube/cache/iso/*or if
minikube deleteand starting it fresh would solve the problem ?