yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  Errored instance can't be deleted if volume deleted first

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  1. Create a bootable volume   "nova volume-create --image-id <image_id> 10"
  2. Boot a vm using the volume created in step 1 " nova boot --flavor 1 --image <image_id> --block-device-mapping vda=<vol_id>:::0 instance1"

  If the instance fails to spawn in step 2, the instance ends up in an
  ERROR state. The volume goes back to available.  The hard part is
  creating a situation in which step 2 fails.  One way is to create
  enough quantum ports to exceed your port quota prior to attempting to
  spawn the instance.

  3. Delete the volume.
  4. Attempt to delete the instance.  An exception gets thrown  by driver.destroy because the volume is not found but the exception is not ignored and the instance can never be deleted.  Exceptions from _cleanup_volumes get ignored for this same reason.  I think another exception handler needs to be added to also ignore VolumeNotFound from driver.destroy.

  I've reproduced this with current code from trunk.

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