Comment 34 for bug 1560965

Akihiro,

I believe this bug nis now longer applies to horizon after patching from comment #20. The nova-compute log shows me correct volume names when the image properties above are applied:

2018-02-26 16:12:19.403 40927 INFO nova.compute.claims [req-70006123-feaa-4f3e-9605-ad28fdbe60cd 33fd8dd8d96f4d17ac5db0c3f600a51e df71265b6e0444a1837f51a14d4c19a8 - default default] [instance: 86c27905-a993-4e21-a1a5-50928922c21e] Claim successful on node compute01.demo.infra.cloud.loc
2018-02-26 16:12:19.774 40927 WARNING nova.virt.libvirt.driver [req-70006123-feaa-4f3e-9605-ad28fdbe60cd 33fd8dd8d96f4d17ac5db0c3f600a51e df71265b6e0444a1837f51a14d4c19a8 - default default] [instance: 86c27905-a993-4e21-a1a5-50928922c21e] Ignoring supplied device name: /dev/sda. Libvirt can't honour user-supplied dev names
2018-02-26 16:12:19.892 40927 INFO nova.virt.block_device [req-70006123-feaa-4f3e-9605-ad28fdbe60cd 33fd8dd8d96f4d17ac5db0c3f600a51e df71265b6e0444a1837f51a14d4c19a8 - default default] [instance: 86c27905-a993-4e21-a1a5-50928922c21e] Booting with blank volume at /dev/sda

So if we split out the bug into two parts - (a) and (b), we drop into (b) and conclude that bug is affected somewhere in nova or libvirt.