-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
addons disable fails: Process exited with status 1 (no useful logs!) #2281
Comments
I haven't found a solution for this yet but I have found a workaround and possibly a suggestion for default behavior for when running "minikube addons disable". The work around I found is to edit .minikube\config\config.json and add the following entry:
So the contents of the file should similar to: {
"kube-dns": false,
"profile": "minikube"
} Obviously the contents of the file may look different. After that you need to restart minikube with the following commands:
Then after the cluster has started eventually the addon will be disabled and eventually the relevant pods etc seem to be terminated, though this can take a minute or too as the pods look like they initially are targeted to get into the running state, then only after they reach that state the changes seem to be applied and they terminate. A suggestion I'd like to make is that when disabling an addon with "minikube addons disable" is that even if minikube fails to find whatever file it seems to be trying to remove and thus fails to disable the addon, that it should change the config.json file anyway setting the plugin to false. Then at least when the cluster is restarted the addon will be disabled eventually rather than never. |
same here |
On 0.24.1 the config file seems to be updated accordingly after running
|
@gtirloni Correct me if I'm wrong but it looks like your using linux/osx, I believe the problem might be specific to windows but I'm unsure. @ambition-consulting Were you also using windows when you encountered the error? |
@rexatorbit that's right, Fedora 27 here. |
@rexatorbit Yes, Windows 10 (with creatorsupdate) with the newest Minikube and Virtualbox while trying to get gofabric8 installed - which is not compatible with k8s 1.8 |
I'm seeing this same issue on Mac OS X now with minikube 0.24.1 running using hyperkit.
Minikube installed with brew cask. Hyperkit installed as binary download. |
Same issue on Windows 10, with minikube 0.24.1: The workaround provided by @rexatorbit works. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Same on 0.26, latest k8s 1.10 |
Same on Windows 10/HyperV [error disabling addon deploy/addons/ingress/ingress-configmap.yaml: Process exited with status 1] minikube version: v0.28.0 |
C:\Users\Sergey.Muha\Minikube>minikube addons disable default-storageclass C:\Users\Sergey.Muha\Minikube> minikube update-check Virtual box - Win10 |
Same here:
minikube version I fixed it by editing .minikube/config/config.json and setting ingress to false then ran |
same on 0.28.2 |
minikube needs to do a much better job of showing error messages here. @den-is mentioned that one last step is required to get rid of kube-dns: kubectl -n kube-system delete deployment kube-dns |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This lifecycle thing is a slap in the face of the userbase. If it's already acknowledged as a bug (type/bug), it makes no sense to close it just because there's no activity. A bug is a bug. |
Does anyone have a repro case for this? I wasn't able to replicate with in v0.33.x, but only because because I couldn't find an addon that failed to disable. |
Minikube version: v1.2.0 OS: Windows 10 Pro Version 10.0.17134 build 17134 minikube addons disable default-storageclass I encountered an unexpected error: C:\Users\cromero\k8s-workshop>minikube addons disable default-storageclass X disable failed: [disabling addon deploy/addons/storageclass/storageclass.yaml.tmpl: Process exited with status 1]
What you expected to happen: How to reproduce it (as minimally and precisely as possible): minikube addons disable default-storageclass No logs were found Should you need further information do not hesitate to ask for it. Cheers |
minikube stop
|
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Please provide the following details:
Environment:
Minikube version: v0.24.1
Copied Minikube.exe straight into windows system32 folder.
What happened:
When trying to disable an addon using the command:
I encountered an unexpected error:
What you expected to happen:
I expected the addon to be disabled successfully.
How to reproduce it (as minimally and precisely as possible):
Simply use a new cluster and try and disable kube-dns with the following command:
Output of
minikube logs
(if applicable):Anything else do we need to know: Also trying to remove other addons does not work.
I have tried clearing the cache and using new profiles still to no avail. I have deleted the whole .minikube and .kube directories from %APPDATA% in windows to force a re-download of iso's etc still to no avail. I updated to the v0.24.1 release as I was also having the same problem in the previous release, but this new release has not helped.
The text was updated successfully, but these errors were encountered: