we could document this corner case better in the docs; and we can mention this in the release notes as a known issue.
I am wondering that maybe partman-lvm could be enchanced to handle this usecase by passing (usually redudandatly the vg_uuid parameter). In practice, there are many corner cases with lvm: e.g. in the past people have tried to use volume groups with clash with device names in /dev or clash with hostname received from DHCP; all of these scenarios lead to LVM installs failing. This is just one more variation on the above. If one uses automated lvm install we try to use a uniquish volume group name, but it is not guaranteed to work given that there are currently no checks on clashing and trying some other name. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679184 Title: LVM configuration cannot be removed when volume groups with the same name are found during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1679184/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
