hyperv: "minikube stop" fails (Shutting down 0% until it eventually times out) #2914
Comments
|
Have rolled back to 0.27.0 to verify that minikube stop works in that version which it does |
|
Same environment and same problem here. Also, if I try to stop minikube from Hyper-V Manager I get the following error:
|
|
This is very likley unrelated to Minikube, as we only issue commands to the
hypervisor. If the manager even fails, it is related to the host and the
hypervisror. Please check your event log on Windows
…On Wed, Jun 20, 2018 at 5:37 AM, Sean Fausett ***@***.***> wrote:
Same environment and same problem here. Also, if I try to stop minikube
from Hyper-V Manager I get the following error:
[image: image]
<https://user-images.githubusercontent.com/750121/41625429-eef6fa90-746c-11e8-895c-95d3f4005973.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2914 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZrFaM4Lf9V_ctu2ejQnJwiUBC2wUks5t-W8UgaJpZM4Utd8V>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
|
I am seeing this issue. Shutdown takes a very long time and fails with this error: Once the shutdown fails, the machine reverts to "running" inside the Hyper-V manager. I then use Hyper-V to turn off the machine. |
|
@gbraad I'll dig a little deeper later but I reverted back to 0.27.0 and it works fine, upgrade to 0.28.0 and it stops working. So there seems to be something unusual going on with 0.28.0 Edited to add, if I connect to the VM and login I can then issue sudo poweroff -p and it shuts down fine. Nothing blatantly obvious in the hyper-v logs, probably closest thing of interest I've found is EDIT: Actually same error is logged for 0.27.0 but it doesn't impact shutdown on that version |
|
i can confirm this is occuring with windows 10 pro 1703 with minikube .28 as well. My error message is:
I will try to update this pc and see if that works, if not i will use the suggested downgrade for minikube. upgrading to 1803 with Minikube v28 had the same results |
|
Quite annoying indeed. I've found to be the fastest workaround. |
|
Thanks for the Is there any further information those of us who have this problem can provide to assist in resolving? I've not seen anything particularly nasty in the event logs or similar... Edit |
|
The same issue with minikube 0.28.0 on windows 10 |
|
@shahiddev I noticed @LazerFX has observed the command shutdown gets scheduled for after one minute. This could mean the shutdown will happen... In code, So, I wonder what causes this difference in behaviour... |
|
@gbraad I've certainly waited for over 1min (in fact over 5mins) and it doesn't shutdown.
I'm preparing for a talk tomorrow so don't want to mess with my minikube installation today but can try and have another go at this later this week. |
|
@gbraad I'm sorry, I don't know what minishift is, but I can certainly try and Google it when I'm in the office on the machine tomorrow, see if I can diagnose the issue. Any tips on what you're looking for, I'd appreciate :-D I'm quite a neophyte to the whole kubernetes infrastructure, so I "don't know what I don't know" as the saying goes - I don't know the holes in my knowledge where I should be able to fill in. |
|
Minishift is a fork of minikube and we share a lot and work together on
issues where possible.
Instead of kubernetes we deploy openshift, which an Enterprise grade
kubernetes deployment.
Details on minishift.io
I haven't see this happen on out tool, but could be related to config. So
this is why I would like you to try.
On Jul 17, 2018 04:37, "Peter Street" <notifications@github.com> wrote:
@gbraad <https://github.com/gbraad> I'm sorry, I don't know what minishift
is, but I can certainly try and Google it when I'm in the office on the
machine tomorrow, see if I can diagnose the issue. Any tips on what you're
looking for, I'd appreciate :-D
I'm quite a neophyte to the whole kubernetes infrastructure, so I "don't
know what I don't know" as the saying goes - I don't know the holes in my
knowledge where I should be able to fill in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2914 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZoGJS81GRhFrjGTZET50xgYSIJj0ks5uHPl4gaJpZM4Utd8V>
.
|
|
Just rolled up a minishift environment, based on minishift version Based on other comments, I also tried the That wasn't there prior to the |
|
Hmmm... so this is very isolated. We (minishift) use the stock libmachine
drivers and library, while minikube pulled them in-repo. I will have a look
if I can find something that can explain this.
…On Tue, Jul 17, 2018 at 8:12 PM, Peter Street ***@***.***> wrote:
Just rolled up a minishift environment, based on minishift version
v1.21.0+a8c8b37, and that is capable of successfully shutting down using minishift
stop.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2914 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZoz1HQ4d6bEsdeCPAwZYV6sE5Ljzks5uHdTHgaJpZM4Utd8V>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
|
looks like minikube 0.28.1 also has this issue. |
|
Was there an update to the ISO for 0.28? Can this be isolated as a potential source - i.e. the OS not responding properly? Can an 0.27 ISO be used on 0.28? |
|
@LazerFX I just did the same thing you did with minikube ssh but I can see that Bash command is already running before the shutdown was initiated. I ran minikube stop in a different window whilst connected via minikube SSH |
|
@gbraad Looks like MiniShift is using the latest version of Docker Machine (0.15) where as Minikube isn't. I wanted to update to the latest version anyway so would it make sense to just update to that? I'm a bit of a noob on this project so don't know the best way of doing that. |
|
We will discuss anyway with @dlorenc to move away from libmachine (to our
fork at machine-drivers/machine) as they entered maintenance mode (no new
features, only bugfixes)... even adding fixes have been slow these days.
…On Thu, Jul 19, 2018, 01:13 Shahid Iqbal ***@***.***> wrote:
@gbraad <https://github.com/gbraad> Looks like MiniShift is using the
latest version of Docker Machine (0.15) where as Minikube isn't. I wanted
to update to the latest version anyway so would it make sense to just
update to that? I'm a bit of a noob on this project so don't know the best
way of doing that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2914 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZk8Mz3Pz4I8QxgfsuEeR8HPPNT_0ks5uH2y-gaJpZM4Utd8V>
.
|
|
Same Problem here:
|
|
Same problem with the same exact information as @saostad. Is there a way to temporarily fix this? |
|
only minikube ssh and then sudo poweroff |
|
@shahiddev That works. I discovered that downgrading works too, though. |
|
You can combine the commands to issue a shutdown in one line:
|
|
Could minikube just be updated to run that command for |
|
Minkube uses docker-machin to issue a shutdown using the hypervisor
management tools. this would be acpi call. Surely minikube could use an
sshcommand instead, but the issue is with submachine... And this library is
in maintenance mode. I also haven't seen this issue with our fork yet...
Which we are in the process of adding to minikube. I'll keep an eye on this
issue and see if the library change fixes this.
On Aug 23, 2018 09:39, "Felix Mattick" <notifications@github.com> wrote:
Could minikube just be updated to run that command for minikube stop?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2914 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZqijtlxNuNFf-pAjewnl8leEiwSmks5uTgfCgaJpZM4Utd8V>
.
|
|
I have exactly the same issue on Windows 10 pro. Stopping the cluster with |
|
Still happening on |
|
@vxavictor513 - Do you mind attaching the output of:
Thanks! |
|
@tstromberg - This is what I got after running the command and waiting for 10 minutes. I force-cancelled the |
|
FWIW, I experienced a lot of these errors when setting up minikube via chocolatey w/ powershell on windows 10. minikube delete followed by recreating eventually worked after a few tries. |
|
Just had a scare with this when the kube wouldn't stop. Just followed the simple steps from the tutorial. Thought a computer restart would do it, but it got stuck at "Restarting your computer" for about 10 minutes. Luckily, though, in the end, it actually restarted. |
|
yeah, I deleted my ~/.minikube folder + minikube virtual machine and run process : minikube start --vm-driver=x --kubernetes-version="vx.xx.x" and works 👍 |
tstromberg
changed the title
|
Same problem here Windows 10 Enterprise 1803 |
|
@tstromberg I have also seen this where the machine in Hyper-V refuses to Power off even from the manager. I tried both |
|
Same problem here Windows 10 Pro 1903 Output from Output from |
|
I have the same versions and issues as @Valgard above, in addition.. I was following the first tutorial (https://kubernetes.io/docs/tutorials/hello-minikube/) and I could enable the heapster addon, but minikube crashed when trying to disable it: |
and others
BUG REPORT
Please provide the following details:
Environment: Windows 10 Pro 1803
Minikube version (use
minikube version): v0.28.0cat ~/.minikube/machines/minikube/config.json | grep DriverName): Hyper-vcat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): v0.28.0What happened: Minikube stop fails to stop minikube VM
What you expected to happen: VM stops
How to reproduce it (as minimally and precisely as possible): With running minikube, perform minikube stop
Output of
minikube logs(if applicable):Anything else do we need to know:
Clean install of Minikube 0.28.0 (deleted .minikube folder)
Command sits with powershell overlay showing Shutting down 0% until it eventually times out
Trying to shutdown via Hyper-V manager/Powershell doesn't work either
Opening VM in hyper-v shows command prompt - may not be relevant?
The text was updated successfully, but these errors were encountered: