Fail to launch an instance from volume by legacy bdm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Feodor Tersin |
Bug Description
Launting an instance from bootable volume passing legacy bdm is available only using vda (no /dev/ prefix) as root device name. This is weird restriction. It prevents to create consistent instance data, because root_device_name instance attribute has /dev/ prefix, but device_name bdm attribute doesn't.
Environment: DevStack
Steps to reproduce:
1 Create bootable volume
$ cinder create --image-id xxx 1
Note: I used cirros-
2 Boot instance from the volume by legacy bdm.
$ nova boot --flavor m1.nano --block-
3 Wait instance status Active, go to instance console and look to 'No bootable device' message.
The reason is in _get_bdm_
Changed in nova: | |
assignee: | nobody → Feodor Tersin (ftersin) |
status: | New → Confirmed |
Changed in nova: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-2 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/95568
Review: https:/