-
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
none: sudo kubeadm init phase certs all --config /var/lib/kubeadm.yaml: exit status #4742
Comments
Seems like there is an unclean previous installation, if you don't care about the contents of the cluster you might want to use |
How to uninstall kubectl and minikube completely ( Including configuration files) ? |
Answered in the other issue: #4765 Did running |
I tried that, but it didn't work. |
The verbose minikube log might have some more clues. |
Thank you for sharing your experience! If you don't mind, could you please provide the output of:
This will help us isolate the problem further. Thank you! |
The issue is resolved, I had exported some wrong file in kubeconfig, I uninstalled the kubectl and reinstalled it got resolved. Thanks for helping me out. |
OS: RHEL 7.2
Minikube version: 1.12
Kubectl version: Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
VM-Driver: None (Because I'm running on AWS instance)
Exact command to replicate this:
sudo -E ./minikube start --vm-driver=none
X Error restarting cluster: running cmd: sudo kubeadm init phase certs all --config /var/lib/kubeadm.yaml: running command: sudo kubeadm init phase certs all --config /var/lib/kubeadm.yaml: exit status 1
The text was updated successfully, but these errors were encountered: