subiquity

(mantic) multipath install fails to boot

Bug #2034606 reported by Paride Legovini
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
Invalid
Undecided
Unassigned
multipath-tools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Tested on:

$ bsdtar -x -f mantic-live-server-amd64.iso -O ./.disk/info
Ubuntu-Server 23.10 "Mantic Minotaur" - Daily amd64 (20230906)

Reproducer:

$ fallocate -l 20G image.img
$ kvm -m 2048 -boot d -cdrom ./mantic-live-server-amd64.iso -device virtio-scsi-pci,id=scsi -drive file=image.img,if=none,id=sda,format=raw,file.locking=off -device scsi-hd,drive=sda,serial=0001 -drive if=none,id=sdb,file=image.img,format=raw,file.locking=off -device scsi-hd,drive=sdb,serial=0001

Before installing jump to a shell and check that the multipath got detected by running `multipath -l`.

Perform an all-defaults install and reboot. As the reboot process begins, ^C the kvm process and re-run the same command changing `-boot d` into `-boot c` (to make it boot from disk).

What I observe: the installed systems fails to boot.

I am sorry I didn't capture install logs yet. I can do that tomorrow if needed. Hopefully the reproducer is enough to triage the bug and maybe start working on it.

Dan Bungert (dbungert)
Changed in subiquity:
status: New → Confirmed
Revision history for this message
Dan Bungert (dbungert) wrote :

Investigated, results as follows:

* lunar live-server is fine
* lunar with main branch subiquity is also fine, so I don't think we've regressed something here
* the oldest mantic live-server I have, 20230801, is also broken
* force installing multipath-tools 0.8.8, by rebuilding for mantic + adjusting the build number higher results in a somewhat working system (mdadm messages: "no arrays found in config or automatically") but does produce a `multipath -l` result

Unclear to me yet if this is outright a regression in the archive or if curtin needs to do something differently for mantic.

Any debugging suggestions for the failed boot scenario?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

So it crashes really quite far into the boot process with all kinds of "buffer I/O error on dev dm-2" messages. Not at all sure what is going on.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Ah the issue here is that some of the initramfs scripts are not executable when they need to be. Kinda crazy failure mode though!

Revision history for this message
Dan Bungert (dbungert) wrote (last edit ):

In additional testing, I have confirmed:

* lunar dist-upgrade - also affected
* mantic with patched multipath-tools, with the initramfs scripts marked executable - install goes correctly

Changed in subiquity:
status: Confirmed → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package multipath-tools - 0.9.4-5ubuntu3

---------------
multipath-tools (0.9.4-5ubuntu3) mantic; urgency=medium

  * d/initramfs/scripts/{local-bottom,local-top}/multipath: Make initramfs
    scripts +x so they actually get executed (Debian changed how initramfs
    scripts are installed in 0.9.0-2 so this matters now but didn't before).
    (LP: #2034606)

 -- Michael Hudson-Doyle <email address hidden> Thu, 07 Sep 2023 11:15:10 +1200

Changed in multipath-tools (Ubuntu):
status: New → Fix Released
Revision history for this message
Paride Legovini (paride) wrote :

Confirmed fixed in the 20230907 ISOs.

The failure mode made this not obvious at all.
Thanks Dan and Michael for the very quick fix!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.