Skip to content
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

gokube reset does not work when the minikube VM is stopped #22

Open
Mvek opened this issue Apr 7, 2021 · 6 comments
Open

gokube reset does not work when the minikube VM is stopped #22

Mvek opened this issue Apr 7, 2021 · 6 comments

Comments

@Mvek
Copy link

Mvek commented Apr 7, 2021

When minikube VM in Oracle VirtualBox is stopped, then gokube reset writes only one or two lines and stops without any message.

First time I did gokube init to solve it, but later I tried first running gokube start and then it worked fine.

@cvila84
Copy link
Collaborator

cvila84 commented Apr 7, 2021

Can you please put hereafter the "lines" you saw to see if the behavior is normal or not ?

@Mvek

This comment has been minimized.

@Mvek
Copy link
Author

Mvek commented Apr 13, 2021

`$ gokube reset
Resetting minikube VM from snapshot...

$
`

That is all and it is displayed immediately after sending gokube reset, when VM is stopped.

@Mvek
Copy link
Author

Mvek commented Apr 13, 2021

Instead of normal (when minikube VM is running):

`$ gokube reset
Stopping minikube VM...

  • Stopping node "minikube" ...
  • 1 nodes stopped.
    Resetting minikube VM from snapshot...
    Starting minikube VM with kubernetes v1.18.15...
    ...`

@cvila84
Copy link
Collaborator

cvila84 commented Apr 13, 2021

This is normal behavior. Reset lets the machine in the same state as it was before being called. So,

  • reset on a running VM will stop the VM (it is not possible restore a snapshot on a running VM), reset it to the saved snapshot and then restart it
  • reset on a stopped VM will reset it to the saved snapshot

@Mvek
Copy link
Author

Mvek commented Apr 13, 2021

That is a good news, now I know I don't have to start the VM again in such case.
But could you then please fix the console output?

In current state it is obvious crash, not a finished script, if last entry ends with ellipsis ...
One line saying snapshot was reset/started/... would be enough and great to avoid misunderstandings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants