diff options
| author | Clay Gerrard <clay.gerrard@gmail.com> | 2012-10-04 18:50:39 -0500 |
|---|---|---|
| committer | Clay Gerrard <clay.gerrard@gmail.com> | 2012-10-04 18:59:43 -0500 |
| commit | 07845ad68f83952bbae36b4b115ff6c433e81fa3 (patch) | |
| tree | 5d5e82b6731287b81aaadff2781193d50e142b42 /nova/openstack | |
| parent | b1896ede6999b37757f73d1a31d53789c341ef7f (diff) | |
| download | nova-07845ad68f83952bbae36b4b115ff6c433e81fa3.tar.gz nova-07845ad68f83952bbae36b4b115ff6c433e81fa3.tar.xz nova-07845ad68f83952bbae36b4b115ff6c433e81fa3.zip | |
Always use bdm in instance_block_mapping on Xen
It doesn't seem that Xen will set the 'root_device_name' property on
instances. This is causing instance_block_mapping to return early
without evaluating the bdm before returning the list of device_names
in use. I'm not sure why instance_block_mapping does this
(optimization?) but on Xen at least it seems that it should not.
Added a check for Xen compute_driver flag in instance_block_mapping to
"guess" the root_device_name (similarlly to what is done in
compute.utils for swap and ephemeral).
fixes bug #1061944
Change-Id: If5b1a2b7377232c78f0629a3624552ecf6ceb0ee
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions