yahoo-eng-team team mailing list archive

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

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

** Changed in: nova
    Milestone: None => grizzly-3

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

Title:
  Add validations to Compute API for block device mappings

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  While booting an instance with block device mappings, certain scenarios need to be 
  taken care of in the Compute API so that Invalid user inputs are avoided and instances do not 
  land up in inconsistent states. 
  We need to add validations in the API to ensure the request body contain correct combinations
  of num_instances and block_device_mappings.

  For example:
  1. Boot multiple instances using a single block device mapping. 
  Current behavior: Only one instance boots successfully with the volume attached to it.
  The other instances fail block device mapping and land up in ERROR state as the volume is "in-use".
  User needs to cleanup ERROR instances.
  API Response: 202 Accepted

  Expected behavior: API should not allow multiple instances to boot
  from same volume.

  2. Boot multiple instances from a list of block device mappings (snapshots or volumes):
  Current behavior: Only one instance boots successfully. Only the second volume in list gets attached to the instance (first one) on vda.
  The other instances fail block device mapping and land up in ERROR state as the volume is "in-use".
  No 1:1 mapping between volume list and instance list
  User needs to cleanup ERROR instances.
  API Response: 202 Accepted
  Expected behavior: API should not allow multiple instances to boot from a list of BDMs 

  
  This was discussed on the mailing list and a need for appropriate API level validations was accepted.
  http://lists.openstack.org/pipermail/openstack-dev/2012-December/004149.html

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