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

Proper debian-9 "shutdown qube"/"kill qube" fails, generates qubesmanager error #3764

Closed
RooneyMcNibNug opened this Issue Mar 30, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@RooneyMcNibNug

Qubes OS version:

Qubes release 4.0 (R4.0)

Affected component(s):

Issue triggered from the debian-9 template, error generated from dom0.


Steps to reproduce the behavior:

Right clicking on the debian-9 template within the Qube Manager GUI and choosing "shutdown qube" doesn't go through with a proper shutdown. After several minutes, I attempted to "kill qube" and was greeted with the error in the Actual behavior section below.

Expected behavior:

The template to shutdown fully/properly.

Actual behavior:

[Dom0] Houston, we have a problem...

Whoops, A critical error has occurred. This is most likely a bug in Qubes Manager.

AssertationError:
at line 772
of file /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py
----
line: assert vm.is_running()
func: action_shutdownvm_triggered
line no.: 772
file: /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py'

General notes:

Logging out and back in again certainly clears everything back to normal, but this issue persists if I go through the same process again afterwards.


Related issues:

@marmarta

This comment has been minimized.

Show comment
Hide comment
@marmarta

marmarta Mar 30, 2018

I have to ask - was the template actually running?

I have to ask - was the template actually running?

@RooneyMcNibNug

This comment has been minimized.

Show comment
Hide comment
@RooneyMcNibNug

RooneyMcNibNug Mar 30, 2018

Yes, it was actually running. The green light indicator was even stuck on next to the respective template until I logged out.

This same issue also just happened to me again but this time with the anon-whonix AppVM - let me know if you want me to try that again later when I have access to the machine and get the error codes, or if you need any other info from my end.

Yes, it was actually running. The green light indicator was even stuck on next to the respective template until I logged out.

This same issue also just happened to me again but this time with the anon-whonix AppVM - let me know if you want me to try that again later when I have access to the machine and get the error codes, or if you need any other info from my end.

@RooneyMcNibNug

This comment has been minimized.

Show comment
Hide comment
@RooneyMcNibNug

RooneyMcNibNug Mar 31, 2018

Seems that these VMs are in fact turning off after many minutes in most cases - just seems that they are taking an extraordinary time to do so. This was not the case with 3.x using the same hardware as now, but I am happy to close this if it seems like less of a system issue.

Seems that these VMs are in fact turning off after many minutes in most cases - just seems that they are taking an extraordinary time to do so. This was not the case with 3.x using the same hardware as now, but I am happy to close this if it seems like less of a system issue.

@marmarta

This comment has been minimized.

Show comment
Hide comment
@marmarta

marmarta Apr 12, 2018

This should be working more correctly now (no errors, at least, although I'm not sure why the longer shutdown times).

It was fixed by QubesOS/qubes-manager#82

This should be working more correctly now (no errors, at least, although I'm not sure why the longer shutdown times).

It was fixed by QubesOS/qubes-manager#82

@marmarta marmarta closed this Apr 12, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment