yahoo-eng-team team mailing list archive

[Lars Kellogg-Stedman <lars@xxxxxxxxxx>]

Public bug reported:

In some situations (using nested KVM in an environment where nested KVM
support is buggy), the appliance started by libguestfs will hang and the
libguestfs-launched qemu process will never exit.  This will cause the
launched instance to get stuck in state=spawning forver (or until
someone explicitly kills the libguestfs appliance).

We should wrap the call to guestfs.Guestfs.launch with some sort of
timeout to detect this situation and at least report an error.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1286256

Title:
  If libguestfs hangs when provisioning an instance, nova will wait
  forever.

Status in OpenStack Compute (Nova):
  New

Bug description:
  In some situations (using nested KVM in an environment where nested
  KVM support is buggy), the appliance started by libguestfs will hang
  and the libguestfs-launched qemu process will never exit.  This will
  cause the launched instance to get stuck in state=spawning forver (or
  until someone explicitly kills the libguestfs appliance).

  We should wrap the call to guestfs.Guestfs.launch with some sort of
  timeout to detect this situation and at least report an error.

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