[Bug 1679184] Re: LVM configuration cannot be removed when volume groups with the same name are found during installation

[Dimitri John Ledkov]

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
Foundations Bugs, which is subscribed to partman-lvm in Ubuntu.
https://bugs.launchpad.net/bugs/1679184

Title:
  LVM configuration cannot be removed when volume groups with the same
  name are found during installation

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  Won't Fix
Status in partman-lvm package in Ubuntu:
  Won't Fix

Bug description:
  Installer version: 20101020ubuntu500

  Kernel: 4.10.0-14

  Description/Reproduction:

  During installation, the installer finds LVM volume groups from a
  previous installation.

  Current LVM configuration:
   Unallocated physical volumes:
     * /dev/mapper/mpatha2                                  (21218MB)
                                                                              
   Volume groups:                                                       
     * rootVG                                               (21218MB)
       - Uses physical volume:         /dev/dasda2          (21315MB)
       - Uses physical volume:         /dev/mapper/mpathc1  (21470MB)
       - Uses physical volume:         [unknown]            (21470MB)
       - Uses physical volume:         [unknown]            (21470MB)
     * rootVG                                               (21470MB)
       - Uses physical volume:         /dev/dasda2          (21315MB)
       - Uses physical volume:         /dev/mapper/mpathc1  (21470MB)
       - Uses physical volume:         [unknown]            (21470MB)
       - Uses physical volume:         [unknown]            (21470MB)
     * rootvg                                               (42685MB)
       - Uses physical volume:         /dev/mapper/mpathb1  (21470MB)
       - Uses physical volume:         [unknown]            (214

  When trying to remove that LVM using "Configure the Logical Volume
  Manager", it is not possible to remove logical volumes. The error "The
  logical volume swapLV on rootVG could not be deleted." is displayed.
  In syslog, you see the following messages:

  Apr  3 12:55:56 partman-lvm:   Multiple VGs found with the same name: skipping rootVG
  Apr  3 12:55:56 partman-lvm:   Use --select vg_uuid=<uuid> in place of the VG name.

  As you cannot use the suggested parameter in the installer, the system
  cannot be installed without manually removing the LVM setup with
  another shell.

  Debug logs are attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1679184/+subscriptions