[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

[Dimitri John Ledkov]

So i think i undid all the bogus red-herring fixes that didn't fix
anything.

and finally uploaded partman-multipath tools that should now work.

tested with Eoan-proposed it all looks good. Please wait for partman-
multipath to publish in eoan release pocket and then retest.

_everything_ should just work. I.e. encrypted lvm on multipath; lvm on
multipath; ecnrypted non-lvm on multipath and so on.

I am not sure about lvm, on encrypted, on raid, on multipath. But i
believe that should also work.

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to partman-multipath 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:
  Confirmed
Status in partman-multipath package in Ubuntu:
  Fix Committed

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