yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

Assuming this is fixed now as it can't be reproduced. Please reopen if
that's not true

** Changed in: nova
       Status: Incomplete => Invalid

** Changed in: nova
     Assignee: Rafi Khardalian (rkhardalian) => (unassigned)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1094398

Title:
  libvirt: Attempting to resume VMs with a corrupt save file is
  irrecoverable

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  If a VM is suspended and the save file becomes corrupt somehow, either
  because it was never saved properly or otherwise, Nova cannot recover.
  It will continue to limit the user to "resume" or "terminate" with no
  option to just reboot without trying to load the save file.  The VM
  will be in this state forever until an admin manually intervenes.  We
  can do better, as the condition is completely recoverable.

  The fix is to add proper exception handling to the driver.resume()
  call such that it catches this case, so that it can clear the saved
  file (equivalent of 'virsh managedsave-remove') and simply start the
  VM normally. The user should probably be notified when this occurs, to
  the effect of the resume having failed but the VM being rebooted
  anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1094398/+subscriptions