yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

No reproduce, incomplete for > 30 days

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

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

Title:
  block_device_mapping_v2 needs better input validation

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  using Havana (2013.2.2) on Ubuntu 12.04 (cloud archive packages)

  It is possible to create an instace that nova believes has a volume
  attached when in fact it is not.  The user is then unable to delete
  the instance becaus enove errors trying to detatch the volume which is
  not attached (deleting the offending volume does allow instancve
  termination but one presumes users want the data on their cinder
  volumes)

  While there are likely deeper causes to this confised state the
  proximal cause appear to be the users specifying "--block-device
  id=<id>,source=volume" on the boot command line rather than "--block-
  device id=<id>,source=volume,dest=volume" which properly attaches the
  requested volume and produces a norally running and normally deletable
  instance.

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