TestVolumeBootPattern.test_volume_boot_pattern fail with libvirt-xen
Bug #1443898 reported by
Anthony PERARD
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Thomas Bechtold | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The following test is failling when runned with libvirt-xen nova compute node.
tempest.
This is due to the function _boot_instance_
Also Nova itself does not reject the device name.
This is with devstack master.
Changed in nova: | |
assignee: | nobody → Anthony PERARD (anthony-perard) |
status: | New → In Progress |
Changed in nova: | |
assignee: | Anthony PERARD (anthony-perard) → nobody |
status: | In Progress → Incomplete |
importance: | Undecided → Low |
Changed in nova: | |
status: | Expired → Confirmed |
To post a comment you must log in.
I try to replace 'device_name': 'vda' in the test by 'device_name': 'xvda', but this leads to an Exception in nova/compute/api.py InvalidBDMBootS equence. This is because boot_index is set to -1 with xvda, instead of 0.
nova is only looking for a device_name equal to 'vda' to be a root device (or root_device_name).
I've search for a way to change root_device_name and it's look like this could be in the volume image metadata 'root_device_name', but I don't know if it's possible to change within the tempest test.