Comment 24 for bug 1813228

OK, with much debugging, I'm going to push the latest bits to address the multipath issue; but this isn't all that's needed and we need some discussion to move forward.

1) The storage config points to a single path, and curtin has added code to detect and determine the main mapping device; we dmsetup remove the partitions and multipath -f the mpath device to clear things before deploying. Ultimately, maas should collect all of the path and mapping info during commissioning and support multipath; for now I suppose this is enough.

2) the maas has a preseed to do some chripl bits; this likely should be pushed into curtin; though we need discussion to know when to do this versus allowing other users (like subiquity) to do it.

3) After install, the first boot is very slow; don't yet know why

4) the network configuration rendered into the target from maas does not match the hardware due to the known firmware issue of shifting MAC values on the interfaces. The result is that network does not match any of the interfaces and no network config is applied.

One approach here is to have maas send a v2 config that matches not on MAC but on path, the zdev device paths are stable.

ethernets:
   encf:
     match:
        path: ccwgroup-0.0.000f
     set-name: encf
     dhcp4: yes