[Bug 1825189] Re: Using full disk encryption, on a multipath device (in this case FCP) ended up in trying to open/unlock a wrong DM device

[Launchpad Bug Tracker]

This bug was fixed in the package parted - 3.2-25ubuntu1

---------------
parted (3.2-25ubuntu1) eoan; urgency=medium

  * _device_get_part_path: use -partN for dm partitions. As otherwise
    there are differences in devices naming between what parted creates,
    and what `udevadm trigger` will rename them to. LP: #1825189

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Mon, 17 Jun 2019 16:21:08
+0100

** Changed in: parted (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  Using full disk encryption, on a multipath device (in this case FCP)
  ended up in trying to open/unlock a wrong DM device

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in debian-installer package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in parted package in Ubuntu:
  Fix Released
Status in partman-base package in Ubuntu:
  Fix Released

Bug description:
  When doing a full disk encrypted installation with d-i using
  "Guided - use entire disk and setup encrypted LVM"
  on a multipath device (in this case zFCP/SCSI)
  the post-install reboot ends in busybox/initramfs
  while trying to open/unlock an incorrect device-maper device.
  initrd tries to open /dev/mapper/mpatha5 but only /dev/mapper/mpatha-part5 exists.

  Fixing the wrong device in crypttab like:
  echo "mpatha5_crypt /dev/mapper/mpatha-part5 none luks,discard" > ./
  cryptroot/crypttab
  and trying to open it manually:
  cryptsetup open --key-file /etc/zkey/repository/mpatha5_crypt.skey --key-size 1024 --cipher paes-xts-plain64 /dev/mapper/mpatha-part5 mpatha5_crypt
  and leaving busybox again seems to work.

  For more details see attachment ...

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