The similar visible issue in the volume information in the instance detail page happens when creating a new server using boot from volume with an existing volume or an existing volume snapshot. For example, when a volume is created based on an image (with hw_disk_bus=scsi and hw_scsi_model=virtio-scsi), these information is stored in cinder volume metadata. When a new server is created from this cinder volume, these metadata is honored. horizon specified 'vda' as device_name, ao a VM itself works well (with /dev/sda) from the same reason described in the previous comment (#59), but the instance detail page says the volume is attached as '/dev/vda'. I will send a fix for this case separately as a follow-up patch of Eric's fix.
The similar visible issue in the volume information in the instance detail page happens when creating a new server using boot from volume with an existing volume or an existing volume snapshot. For example, when a volume is created based on an image (with hw_disk_bus=scsi and hw_scsi_ model=virtio- scsi), these information is stored in cinder volume metadata. When a new server is created from this cinder volume, these metadata is honored. horizon specified 'vda' as device_name, ao a VM itself works well (with /dev/sda) from the same reason described in the previous comment (#59), but the instance detail page says the volume is attached as '/dev/vda'. I will send a fix for this case separately as a follow-up patch of Eric's fix.