I agree with the NIC always booting first, my patch only intended to correct the device order in the VM because this is influenced by the boot.priority.
Perhaps I can simplify my bug report to be:
When I compose and deploy (with no further storage config)
maas vm-host compose 11 storage=‘10(default),11(default),12(default)’
The boot + root disk should be the first device specified in this list with 10Gb. The issue is that the second device in this list ends up as the root/boot device with 11Gb.
I agree with the NIC always booting first, my patch only intended to correct the device order in the VM because this is influenced by the boot.priority.
Perhaps I can simplify my bug report to be:
When I compose and deploy (with no further storage config) ‘10(default) ,11(default) ,12(default) ’
maas vm-host compose 11 storage=
The boot + root disk should be the first device specified in this list with 10Gb. The issue is that the second device in this list ends up as the root/boot device with 11Gb.