-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Kubernetes not working after hard shutdown #404
Comments
Hmm, I just tried and wasn't able to repro this. Did you happen to run "minikube logs" before the delete? |
@dlorenc It may be unrelated to the upgrade procedure, as I just had this happen again with Here is the output of
I had previously hard-shutdown my Mac, so my guess is this caused irreparable corruption. I wasn't expecting kubernetes (via etcd) to be corrupted so easily, though. Is it expected that a single-node kubernetes cluster (e.g. minikube) cannot withstand a hard shutdown? This may be related to etcd-io/etcd#5857 and etcd-io/etcd#5862, but I don't know enough about etcd to say -- if anyone knows better, please chime in! |
I am able to reproduce this by having a misconfigured 3rd party resource in my kubernetes cluster. My only solution to this is to delete/reistall minikube. from minikube logs: 016-10-31 20:23:15.174411 I | etcdserver: recovered store from snapshot at index 590059 goroutine 191 [running]: ==> /var/lib/localkube/localkube.out <== minikube version |
Possibly related to #660 |
I got the same issue, but I did not hard shut down my OS. I'm running it on OS X, after I start the cluster use "minikube start", I got this: $ minikube logs |
@philipn It seems my api server:8080 is not started correctly, like your 8443. Did you get any progress on this? |
@cuiyz It hasn't happened to me since my reports earlier. I'm still on the same minikube version as when reported. I wasn't able to reproduce similar corruption behavior in repeated hard (partial and full) cluster shutdown tests of our production K8s cluster, so I didn't investigate this further. I'll comment here again if I see this happen again on a newer minikube release (I'm on v0.7.0 for parity with our production K8s). |
@philipn you can continue to use new versions of minikube while pinning a kubernetes version
|
This should be fixed in 0.19.1 |
I just upgraded to minikube 0.7.0 from 0.6.0. I'm on OS X and I installed using the OS X installation instructions. To upgrade, I ran the OS X curl installation instructions. My minikube machine was running at the time I attempted my upgrade.
After upgrade, I see:
My workaround was to run
minikube delete; minikube start
and then re-create my kubernetes cluster.The text was updated successfully, but these errors were encountered: