block_device_mapping_v2 boot_index not respected by libvirt driver
Bug #1229327 reported by
Dennis Kliban
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Nikola Đipanov |
Bug Description
block_device_
The expected boot order in the above snippet is hd (glance image), cdrom, floppy. However, when the instance starts it attempts to boot from hd and then floppy. The problem lies here: https:/
The boot device is always set to 'hd'. The driver should support a list of boot devices based on the boot_index supplied in block_device_
Changed in nova: | |
assignee: | nobody → Nikola Đipanov (ndipanov) |
tags: | added: libvirt |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
milestone: | none → icehouse-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
pasting the block_device_ mapping_ v2 here so it doesn't get lost:
block_ device_ mapping_ v2 = [ n_type" : "volume", e4e1-4156- 95ca-bf0aa80c47 b6", n_type" : "volume", 4f80-4471- a77d-23ad751271 38",
{"source_type": "volume",
"destinatio
"uuid": "04e0887c-
"boot_index": "1",
"device_type": "cdrom",
"volume_size": "3",
"disk_bus": "ide",
},
{"source_type": "volume",
"destinatio
"uuid": "be2b7c60-
"boot_index": "2",
"device_type": "floppy",
"volume_size": "1",
"device_name": "/dev/fd0",
},
]