FWIW I don't see any changes to the disk ordering that could cause this in my devstack env:
$ sudo virsh domblklist 8ddce596-52f7-4e60-b714-11f60a4ab8d8 Target Source ------------------------------------------------ vda vms/8ddce596-52f7-4e60-b714-11f60a4ab8d8_disk vdb volumes/volume-ba7486b3-4ea5-4715-89f3-1ec86b0d9812
$ nova reboot --hard 8ddce596-52f7-4e60-b714-11f60a4ab8d8 Request to reboot server test (8ddce596-52f7-4e60-b714-11f60a4ab8d8) has been accepted.
FWIW I don't see any changes to the disk ordering that could cause this in my devstack env:
$ sudo virsh domblklist 8ddce596- 52f7-4e60- b714-11f60a4ab8 d8 ------- ------- ------- ------- ------- ------ 52f7-4e60- b714-11f60a4ab8 d8_disk volume- ba7486b3- 4ea5-4715- 89f3-1ec86b0d98 12
Target Source
-------
vda vms/8ddce596-
vdb volumes/
$ nova reboot --hard 8ddce596- 52f7-4e60- b714-11f60a4ab8 d8 52f7-4e60- b714-11f60a4ab8 d8) has been accepted.
Request to reboot server test (8ddce596-
$ sudo virsh domblklist 8ddce596- 52f7-4e60- b714-11f60a4ab8 d8 ------- ------- ------- ------- ------- ------ 52f7-4e60- b714-11f60a4ab8 d8_disk volume- ba7486b3- 4ea5-4715- 89f3-1ec86b0d98 12
Target Source
-------
vda vms/8ddce596-
vdb volumes/