Project

General

Profile

Bug #73776

Docker Host VM state doesn't update properly

Added by Timothy Moore II 14 days ago. Updated 8 days ago.

Status:
Blocked
Priority:
No priority
Assignee:
William Grzybowski
Category:
GUI (new)
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Waiting for feedback
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Testing with a FreeNAS Mini installed with 11.2-U2-INTERNAL84:

I created a Docker Host vm and started it. The "State" column in the Virtual Machines table shows the process: the VM moved from STOPPED > STARTING > RUNNING.

I click Options > Stop for the RUNNING VM. The "State" moves from RUNNING > STOPPING > RUNNING. I check the Serial connection and the VM appears to be running normally with no indications it is shutting down. I click Options > Stop again for the VM, but this time the "State" never updates and remains as RUNNING. I click to a different UI screen and return to Virtual Machines. The table now appears correctly, with the Docker Host VM showing a "State" of STOPPED.

testvms.png (52.7 KB) testvms.png Timothy Moore II, 02/05/2019 12:02 PM
testvm-states.png (20.2 KB) testvm-states.png Timothy Moore II, 02/05/2019 12:02 PM
52426
52428

History

#1 Updated by Timothy Moore II 14 days ago

  • Subject changed from Docker Host VM doesn't stop properly to Docker Host VM state doesn't update properly

#2 Updated by Dru Lavigne 14 days ago

  • Assignee changed from Release Council to Erin Clark
  • Target version changed from Backlog to 11.2-U3

#3 Updated by Vladimir Vinogradenko 10 days ago

  • Assignee changed from Erin Clark to Vladimir Vinogradenko

#4 Updated by Vladimir Vinogradenko 8 days ago

  • Status changed from Unscreened to Blocked
  • Reason for Blocked set to Waiting for feedback

#5 Updated by Vladimir Vinogradenko 8 days ago

  • Assignee changed from Vladimir Vinogradenko to William Grzybowski

William, please let me know what you think.

1. New UI has states "STARTING" and "STOPPING", middleware does not. I think it makes sense to support these states on middleware side. Right now the following happens:

  • User clicks "stop" button, UI shows "STOPPING" state
  • UI does periodic vm.query and shows "RUNNING" state again

2. ACPI shutdown can hang forever. Like when you shut down system that is still booting and acpid is not started yet. Or guest system does not have acpid ot all. Or guest system is unresponsive, or there is a bug in guest system init, or million other reasons. We can probably add some force-timeout=300 option to stop method that will, if ACPI shutdown fails in timeout second, pull the power cord from VM.

Also available in: Atom PDF