This still exists in at least version 2.3.5 (6511-gf466fdb-0ubuntu1).
Deploying to a machine with multiple disks automatically put the OS on the "wrong" disk (i.e. not the one I wanted to use).
Manually creating an ext4 partition on the desired disk and setting it as "/" didn't result in any errors, but the deploy failed.
Removing the first partition, then creating a 500MB vfat partition to mount as /boot/efi and then a second ext4 partition as "/" solved the problem.
This is an IPMI-controlled machine with "Power boot type" set to EFI, so MAAS should be aware that an EFI partition is required.
This still exists in at least version 2.3.5 (6511-gf466fdb- 0ubuntu1) .
Deploying to a machine with multiple disks automatically put the OS on the "wrong" disk (i.e. not the one I wanted to use).
Manually creating an ext4 partition on the desired disk and setting it as "/" didn't result in any errors, but the deploy failed.
Removing the first partition, then creating a 500MB vfat partition to mount as /boot/efi and then a second ext4 partition as "/" solved the problem.
This is an IPMI-controlled machine with "Power boot type" set to EFI, so MAAS should be aware that an EFI partition is required.