** Also affects: nova/juno
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New => Fix Committed
** Changed in: nova/juno
Milestone: None => 2014.2.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/1417239
Title:
Duplicated block_device_mapping entries with cells
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) juno series:
Fix Committed
Bug description:
People running Nova with cells are affected by this bug.
The bug can be reproduced by booting an instance from a volume with a
block device mapping missing the device name. Although the instance
boots fine, you won't be able to create an image from the instance.
This is because 2 block_device_mapping entries are created in the API cell:
- one (created by the API cell) will have close to no information about the
volume (device_name and volume_id are NULL)
- the second one (bubbled up from the compute cell) will contain all the
volume information
The first entry confuses Nova when creating an image since it won't be
able to find the associated volume (NULL) in Cinder:
ERROR: Block Device Mapping is Invalid: failed to get volume XXX.
(HTTP 400)
The fix is to not create the first block_device_mapping entry and let
the compute cell sync it up to the API cell once created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1417239/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
