subiquity crashes when attempting advanced network/disk configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Subiquity for 20.04 crashes and a system install attempt fails when attempting to do an install with a complex network or disk configuration.
When attempting an install with a semi-complex configuration (e.g. multiple network interfaces bonded together using LACP or multiple partitions with LVM, tmpfs, and swap), the installer will crash and fail.
I am attempting an automated install using ISOs generated by the scripts at https:/
So the (admittedly very obscure) error is that we don't know what to make of this device:
P: /devices/ virtual/ block/dm- 8 /devices/ virtual/ block/dm- 8 D=6700470 DISABLE_ SUBSYSTEM_ RULES_FLAG= 1 DISABLE_ DISK_RULES_ FLAG=1 DISABLE_ OTHER_RULES_ FLAG=1 /dev/mapper/ ventoy
N: dm-8
L: 0
S: mapper/ventoy
E: DEVPATH=
E: SUBSYSTEM=block
E: DEVNAME=/dev/dm-8
E: DEVTYPE=disk
E: MAJOR=253
E: MINOR=8
E: USEC_INITIALIZE
E: DM_UDEV_
E: DM_UDEV_
E: DM_UDEV_
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_NAME=ventoy
E: DM_SUSPENDED=0
E: DEVLINKS=
E: TAGS=:systemd:
What is it? I can't tell from this fragment! (Not really sure how you get a device-mapper device without a DM_UUID entry in udev but maybe I'm misunderstanding something)