[Bug 1570580] Re: Existing Logical Volumes on multipathed SCSI disks are not automatically activated during installation

[Dimitri John Ledkov]

I believe i have managed to reproduce this issue now.
So logical volumes are detected correctly and are present in e.g. "Configure LVM" sub-menu; but they do not appear in the manual partitioning screen.

I did: "rm /var/lib/partman/lvm" in the d-i manual shell, and executed
detect disks again and they have appeared in the manual partitioning
step. So clearly, LVM detection does not happen again after multipath
devices have been assembled. Investigating further now.

** Changed in: debian-installer (Ubuntu)
       Status: Incomplete => Confirmed

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1570580

Title:
  Existing Logical Volumes on multipathed SCSI disks are not
  automatically activated during installation

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  Installer version: 447
  Kernel: 4.4.0.18
  Description/Reproduction:
  Logical Volumes that exist on multipathed SCSI disks from a previous installation are not automatically activated and thus can not be reused. Only the partitions are visible and that their type is "lvm" (s. screenshot). 

  Workaround:

  When the partitioned disks are shown in the "Partition disks" menu,
  open a shell. Then list all logical volumes with command lvs, and set
  each logical volume active with lvchange -ay
  <volumegroupname>/<lvolname>. Choose "Configure the Logical Volume
  Manager", confirm keeping current partition layout with "Yes"  and
  "Finish" without changing anything. Then the Logical Volumes are
  displayed in the "Partition disks" menu and filesystems can be created
  and mountpoints defined.

  I will attach syslog and partman of the installation attempt.

  So obviously an lvchange -ay on all detected lolgical volumes is
  missing at the proper time....

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570580/+subscriptions