Comment 23 for bug 1902855

> The intent is that what mulitpath-tools does on boot is reflected
> in the installer. If it is disabled by kernel command line or
> whatever, the disks should not be multipathed. It's possible this
> is not what happens, but it's not by design.

yes, that's what is not working. with multipath disabled on the command line, I see:

Nov 06 11:11:08 | libdevmapper version 1.02.167 (2019-11-30)
Nov 06 11:11:08 | DM multipath kernel driver not loaded
===== paths list =====
uuid hcil dev dev_t pri dm_st chk_st vend/prod/rev
     0:1:1:1 nvme0n1 259:0 -1 undef undef NVME,Force MP600
     1:1:1:1 nvme1n1 259:1 -1 undef undef NVME,Seagate FireCuda 520 SSD ZP20
     2:1:1:1 nvme2n1 259:2 -1 undef undef NVME,Force MP600
     1:0:0:0 sda 8:0 -1 undef undef ATA,WDC WD141KRYZ-01
     6:0:0:0 sdb 8:16 -1 undef undef ATA,WDC WD141KRYZ-01

as seen in the crash report, all multipath queries are answered with no, then the installer tries to run multipath ...