Comment 32 for bug 1560965

We switched from Xen to KVM a couple of months ago, so I won't be able to test any changes, at least not easily. I can check if we have a spare compute node for testing purposes.

Someone already confirmed this for Ocata, too, but I just ran another test in our environment. I don't know if I can really clarify anything because the used source code has changed in the last two years and in the meantime my own patch doesn't even work anymore, the patch from #20 also fails.

I have a base image with these properties:
'hw_scsi_model': 'virtio-scsi', 'hw_disk_bus': 'scsi'

I launch an instance from that image to a volume and the instance gets it right:

boot-from-vol:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 11G 0 disk
├─sda1 8:1 0 501M 0 part /boot
└─sda2 8:2 0 9,5G 0 part
  ├─vg0-usr 254:0 0 3G 0 lvm /usr
  ├─vg0-root 254:1 0 1,4G 0 lvm /
  ├─vg0-tmp 254:2 0 1G 0 lvm /tmp
  └─vg0-var 254:3 0 1,6G 0 lvm /var

But Horizon shows /dev/vda as the attached volume.
Attaching a second (empty) volume is correctly processed as sdb within the VM:

boot-from-vol:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 11G 0 disk
├─sda1 8:1 0 501M 0 part /boot
└─sda2 8:2 0 9,5G 0 part
  ├─vg0-usr 254:0 0 3G 0 lvm /usr
  ├─vg0-root 254:1 0 1,4G 0 lvm /
  ├─vg0-tmp 254:2 0 1G 0 lvm /tmp
  └─vg0-var 254:3 0 1,6G 0 lvm /var
sdb 8:16 0 1G 0 disk

but from Cinder/Horizon perspective it's attached as /dev/sda. A reboot of the VM succeeds without failures.

The patch doesn't work anymore (openSUSE Leap 42.3). I'm not able to tell if a split of the issue(s) is recommended, I would leave that for the developers to decide.
I guess I didn't really clear anything up, but maybe this will get fixed anyway.