[Bug 1914812] Re: curtin fails to deploy centos 8 on nvme with multipath from ubuntu 20.04

[Alexsander de Souza]

** Changed in: maas/3.3
    Milestone: 3.3.x => 3.3.5

** Changed in: maas/3.3
       Status: Fix Committed => Fix Released

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

Title:
  curtin fails to deploy centos 8 on nvme with multipath from ubuntu
  20.04

Status in curtin:
  Won't Fix
Status in MAAS:
  Fix Committed
Status in MAAS 3.3 series:
  Fix Released
Status in MAAS 3.4 series:
  Fix Released

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1891718 aka
  https://github.com/rhboot/efivar/pull/158 is not fixed in centos.

  centos 8 does not support multipath nvme.

  ubuntu 20.04 supports multipath nvme.

  efibootmgr in a centos chroot, when booted into ubuntu 20.04 kernel
  fails to create efibootmgr entry for the multipath nvme drive.

  efibootmgr on ubuntu 20.04 can create correct entry for the mulipath
  nvme drive, and the entry is universal one (based on gpt uuids, rather
  than anything nvme specific). Thus it does not matter which efibootmgr
  is used to create it.

  But since the centos one is buggy, we should be installing efiboogmgr
  in the ephemeral environment and using that one; instead of the buggy
  one inside the centos chroot.

  as a workarounds one can
  * choose non-nvme drive as the boot device
  * use ubuntu 18.04 or older as the ephemeral provisioning enviornment
  * in maas set to boot ephemeral environment with kernel argument
    "nvme-core.multipath=0"
  * ask RHEL to fix their stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1914812/+subscriptions