Duplicated block_device_mapping entries with cells
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Mathieu Gagné | ||
Juno |
Fix Released
|
Undecided
|
Mathieu Gagné |
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_
- 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_
tags: | added: juno-backport-potential |
Changed in nova: | |
assignee: | Mathieu Gagné (mgagne) → Nikola Đipanov (ndipanov) |
Changed in nova: | |
assignee: | Nikola Đipanov (ndipanov) → Mathieu Gagné (mgagne) |
Changed in nova: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/152257
Review: https:/