Not possible to spawn vmware instance with multiple disks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Thang Pham |
Bug Description
The behaviour of spawn() in the vmwareapi driver wrt images and block device mappings is currently as follows:
If there are any block device mappings, images are ignored
If there are any block device mappings, the last becomes the root device and all others are ignored
This means that, for example, the following scenarios are not possible:
1. Spawn an instance with a root device from an image, and a secondary volume
2. Spawn an instance with a volume as a root device, and a secondary volume
The behaviour of the libvirt driver is as follows:
If there is an image, it will be the root device unless there is also a block device mapping for the root device
All block device mappings are used
If there are multiple block device mappings for the same device, the last one is used
The vmwareapi driver's behaviour is surprising, and should be modified to follow the libvirt driver.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
importance: | Medium → High |
assignee: | nobody → Arnaud Legendre (arnaudleg) |
Changed in nova: | |
assignee: | Thang Pham (thang-pham) → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
assignee: | Davanum Srinivas (DIMS) (dims-v) → Thang Pham (thang-pham) |
Changed in nova: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-3 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/95858
Review: https:/