> This is in an integration lab so these hosts (including maas) are stopped, > MAAS is reinstalled, and the systems are redeployed without any release > or option to wipe during a MAAS release. > Then MAAS deploys Bionic on these hosts thinking they are completely new > systems but in reality they still have the old volumes configured. MAAS > configures the root disk but nothing to the other disks which are > provisioned through other automation later.
Even with a system as you describe, curtin will erase all metadata as configured. I do not believe that after deployment that any LVM devices will be present on the booted system or found with LVM scan tools. I very much would like to see the curtin install log from the scenario you describe and any "old volumes" that appear configured after the install. If some post-deployment script starts creating VGs and LVs, it's possible the could find some metadata that curtin did not detect (offsets further into the disk. MAAS and curtin aren't responsible for wiping the entire contents of the disk *unless* told to do so. Curtin accepts config like: wipe: zero Which will zero out the entire device (disk, partition, etc). However such wipes may take very long. I do not think this is a useful setting. Instead the post-deployment scripts should be using best-practices, just like curtin does when dealing with reused storage. Note that: 1) LVM tools *warn* when it finds existing metadata 2) All lvm tools include a --zero flag which will remove existing metadata before creating; this is best practice when re-using existing storage. Curtin also pre-wipes disks and partitions at their location in the disk before creating things on top specifically to prevent buried metadata from causing issues when creating new composed devices. So please do find out more details about the post-install deployment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
