Comment 17 for bug 2058511

This is sort of the same as 'part of' my bug report: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2065236

But my write-up of that is that there is a bigger problem with the new partitioner.

It's not just NOT recognizing LVM2 structures. It's also not recognizing mdadm, and LUKS containers, etc. So there is a bigger problem where it is not recognizing many volume managers, file systems types, and storage containers, that it used to be able to with the older partitioner.

I will link this bug to mine, (as a mention) since this 'IS' older... but there is still a bigger problem that needs to be addressed with this.

The autoinstall example buried deeply within the snap image work, as an alternate method. They are undocumented.

Eevn though they work as a workaround, they don't address the problem with the new partioner not being able to recognize pre-existing storage containers. That was something that Canonical promised that they would improve and fix when they announced choosing the new partitioner, back in the Lunar DEV-Cycle. So far none of that has transpired.