[Bug 1798512] Re: [ppc64el] LVM+crypto on ppc64el points to an invalid crypto_source

[Mathieu Trudel-Lapierre]

partman-crypto looks fine at first glance, but I'm starting to suspect
multipath-tools might be addressing devices differently in d-i; possibly
because of how we build the udeb, or what we have in multipath.conf?

** Also affects: multipath-tools (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: multipath-tools (Ubuntu)
       Status: New => Incomplete

** Changed in: partman-crypto (Ubuntu)
       Status: New => Incomplete

** Changed in: multipath-tools (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [ppc64el] LVM+crypto on ppc64el points to an invalid crypto_source

Status in multipath-tools package in Ubuntu:
  Incomplete
Status in partman-crypto package in Ubuntu:
  Incomplete

Bug description:
      4.582154]    8regs     : 17120.000 MB/sec
  [    4.622155]    8regs_prefetch: 15152.000 MB/sec
  [    4.662154]    32regs    : 17968.000 MB/sec
  [    4.702155]    32regs_prefetch: 16512.000 MB/sec
  [    4.742155]    altivec   : 26000.000 MB/sec
  [    4.742202] xor: using function: altivec (26000.000 MB/sec)
  [    4.743182] async_tx: api initialized (async)
  done.
  Spawning shell within the initramfs

  
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) grep -r mpatha3 *
  cryptroot/crypttab:mpatha3_crypt /dev/mapper/mpatha3 none luks,discard

  
  Boot reproducibly fails because it can't find /dev/mapper/mpatha3. This is expected, since after install the device is named mpatha-part3.

  We really need to standardize on the naming...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1798512/+subscriptions