Reviewed: https://review.openstack.org/402318 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=12485c74faf317dfe2c05ee0b4877412002893d6 Submitter: Jenkins Branch: master
commit 12485c74faf317dfe2c05ee0b4877412002893d6 Author: Thomas Bechtold <[email protected]> Date: Thu Nov 24 17:04:37 2016 +0100 Fix root_device_name for Xen When running the Tempest scenario test_volume_boot_pattern.\ TestVolumeBootPattern.test_volume_boot_pattern with a libvirt+Xen environment, the tests fails because the root_device_name is set to 'vda' which is invalid for Xen. When getting the BDM for the root block device, check that the root_device_name is compatible with the used disk bus and if it is not, adjust the root_device_name. Change-Id: I4c231b5ef646a067be1566653b6ee89ccbee60f3 Closes-Bug: #1443898 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1443898 Title: TestVolumeBootPattern.test_volume_boot_pattern fail with libvirt-xen Status in OpenStack Compute (nova): Fix Released Status in tempest: Invalid Bug description: The following test is failling when runned with libvirt-xen nova compute node. tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern This is due to the function _boot_instance_from_volume which create a volume with the device name "vda", but this is not supported by Xen. Also Nova itself does not reject the device name. This is with devstack master. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1443898/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
