> Xenial deploy currently works when using MAAS Version 1.9.4+bzr4592-0ubuntu1 (trusty1)
so...did this *ever* work with maas 2.1.2?
> no disk with serial 'CVMD434500BN400AGN' found
if curtin in maas 2 is using the /dev/disk/by-id/nvme-SERIAL symlink to find the nvme drive, then this is definitely the same as bug 1642903 - and if your NVMe drive(s) have spaces in their model or serial strings, you need bug 1647485 as well.
Additionally, if you're deploying trusty (and if curtin expects the by-id symlinks) then you'll need the 3.13.0-107 kernel which is still in -proposed (from bug 1649635).
I believe curtin was changed a while ago to use the /dev/disk/by-id/ symlink(s), but possibly maas 1.9 still has a curtin that doesn't use the by-id symlinks? That would explain the difference. However, if this worked with maas 2.1.2 very recently, then something else entirely is going on.
> Xenial deploy currently works when using MAAS Version 1.9.4+bzr4592- 0ubuntu1 (trusty1)
so...did this *ever* work with maas 2.1.2?
> no disk with serial 'CVMD434500BN40 0AGN' found
if curtin in maas 2 is using the /dev/disk/ by-id/nvme- SERIAL symlink to find the nvme drive, then this is definitely the same as bug 1642903 - and if your NVMe drive(s) have spaces in their model or serial strings, you need bug 1647485 as well.
Additionally, if you're deploying trusty (and if curtin expects the by-id symlinks) then you'll need the 3.13.0-107 kernel which is still in -proposed (from bug 1649635).
I believe curtin was changed a while ago to use the /dev/disk/by-id/ symlink(s), but possibly maas 1.9 still has a curtin that doesn't use the by-id symlinks? That would explain the difference. However, if this worked with maas 2.1.2 very recently, then something else entirely is going on.
I can't tell with the information provided.