Comment 4 for bug 1560965

Hi Paul,

> 1) Should this bug not be logged against Horizon rather than Nova?

In my opinion, the faulty behavior in Horizon is only a result of the wrong device name selection by libvirt. If Horizon provides the wrong device name it should be checked within libvirt (nova) and then pick a correct name. But I'm hoping for the professionals here to correct me as I'm quite new to Openstack.

> 2) Is setting the initial device_name in Horizon to blank not enough to make libvirt autoselect the boot device?

By default, you can't provide your own device name as the respective field is blank. So if you launched a VM from volume via Horizon, you would always have the default device_name "vda" passed to nova, which would lead to the termination of that VM. I only made that field visible for testing purposes because I don't want users to bother about device names. That's why I set the default device_name to blank.

> 3) you set the "Device Name" field in Horizon to visible - could you let me know how you did this?

Sure:
control1:~ # diff -u /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py.dist
--- /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py 2016-03-29 14:49:07.583429716 +0200
+++ /srv/www/openstack-dashboard/openstack_dashboard/local/local_settings.py.dist 2016-03-22 11:50:52.832377033 +0100
@@ -203,7 +203,7 @@
 # can_set_mount_point to True will add the option to set the mount point
 # from the UI.
 OPENSTACK_HYPERVISOR_FEATURES = {
- 'can_set_mount_point': False,
+ 'can_set_mount_point': True,
     'can_set_password': False,
     'requires_keypair': False,
 }