You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It worked as expected - the VM was created and the cluster was up and running.
Then I tried to shut down the cluster using
minikube stop
The command was hang at 0% for ages and finally end up with the clash report. During the time of waiting, in the Hyper-V manager, I could see the status of the VM was changed to "Shutting down", but the CPU usage was quite low so it didn't look like doing anything. At the end I had to connect to the VM and use shutdown command to turn off the VM.
What you expected to happen:
The cluster should be shutdown as expected.
How to reproduce it (as minimally and precisely as possible):
Simply use the pair of "minikube start ..." and "minikube stop" with parameters as specified above.
Output of minikube logs (if applicable):
Anything else do we need to know:
Rolled back to v0.27.0 and deleted the VM and the %USERDATA%/.kube and .minikube folders to start from scratch. v0.27.0 just worked perfectly as expected.
The text was updated successfully, but these errors were encountered:
This is a BUG REPORT:
Please provide the following details:
Environment:
Minikube version (use
minikube version
): v0.28.0cat ~/.minikube/machines/minikube/config.json | grep DriverName
): Hyper-Vcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): defaultWhat happened:
I created the k8s cluster using the command
minikube start --vm-driver="hyperv" --hyperv-virtual-switch="minikube" --kubernetes-version="v1.9.4" --memory=4096
It worked as expected - the VM was created and the cluster was up and running.
Then I tried to shut down the cluster using
minikube stop
The command was hang at 0% for ages and finally end up with the clash report. During the time of waiting, in the Hyper-V manager, I could see the status of the VM was changed to "Shutting down", but the CPU usage was quite low so it didn't look like doing anything. At the end I had to connect to the VM and use shutdown command to turn off the VM.
What you expected to happen:
The cluster should be shutdown as expected.
How to reproduce it (as minimally and precisely as possible):
Simply use the pair of "minikube start ..." and "minikube stop" with parameters as specified above.
Output of
minikube logs
(if applicable):Anything else do we need to know:
Rolled back to v0.27.0 and deleted the VM and the %USERDATA%/.kube and .minikube folders to start from scratch. v0.27.0 just worked perfectly as expected.
The text was updated successfully, but these errors were encountered: