(comment on horizon)
As of stein/train release, this issue does not affect VM spawning. It just affects volume information of the instance detail page (and the output of "nova volume-attachments <server-id>"). Eric's fix in horizon will address it. Even if "nova volume-attachments <server-id>" and the instance detail page say /dev/vda, a volume is attached as /dev/sda inside a VM and the VM successfully launched (I tested with cirros image from devstack). I guess this is because of the fact "Note that as of the 12.0.0 Liberty release, the Nova libvirt driver no longer honors a user-supplied device name" (as described in the Nova API reference [1]).
(comment on horizon)
As of stein/train release, this issue does not affect VM spawning. It just affects volume information of the instance detail page (and the output of "nova volume-attachments <server-id>"). Eric's fix in horizon will address it. Even if "nova volume-attachments <server-id>" and the instance detail page say /dev/vda, a volume is attached as /dev/sda inside a VM and the VM successfully launched (I tested with cirros image from devstack). I guess this is because of the fact "Note that as of the 12.0.0 Liberty release, the Nova libvirt driver no longer honors a user-supplied device name" (as described in the Nova API reference [1]).
[1] https:/ /developer. openstack. org/api- ref/compute/ ?expanded= create- server- detail