I discussed this with cgregan on IRC and I think we came to the conclusion that the MAAS/curtin bug is simply that the two kernels (commissioning vs. ephemeral deployment) gather different (or missing) unique identifiers for each drive.
To validate that, I would run the following on each kernel on the problematic systems:
find /dev/disk -type l | xargs ls -1l | awk '{ print $9, $10, $11 }' | sort -k2
This will tell us which unique identifiers each kernel found to identify each disk, and sort by the endpoint block device, to make it easier to identify what might be missing for each drive.
I discussed this with cgregan on IRC and I think we came to the conclusion that the MAAS/curtin bug is simply that the two kernels (commissioning vs. ephemeral deployment) gather different (or missing) unique identifiers for each drive.
To validate that, I would run the following on each kernel on the problematic systems:
find /dev/disk -type l | xargs ls -1l | awk '{ print $9, $10, $11 }' | sort -k2
This will tell us which unique identifiers each kernel found to identify each disk, and sort by the endpoint block device, to make it easier to identify what might be missing for each drive.