fails to configure BOOTIF when using iscsi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Fix Committed
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned | ||
open-iscsi (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
New
|
Undecided
|
Unassigned | ||
Jammy |
New
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
* MAAS cannot PXE-boot a machine that has iSCSI disks
* Focal is the default Ubuntu distribution deployed by MAAS, so we should
back-port this to ensure it works out-of-the-box.
[ Test Plan ]
* reproducing this issue requires a machine with iSCSI disks (Cisco UCS Manager
in the original report), and a MAAS controller (3.4 or better)
* the issue can be observed by simply enlisting the machine in MAAS. It will
fail to boot due to the missing BOOTIF configuration.
[ Where problems could occur ]
* the problematic code was an attempt to fix LP#2037202, so we should watch out
for regressions.
[ Original report ]
we have a bad interaction between initramfs-tools and open-iscsi, resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from open-iscsi creates a /run/net-
for x in /run/net-
if [ -e "$x" ]; then
fi
done
tags: | added: patch |
Changed in initramfs-tools (Ubuntu): | |
status: | Triaged → Fix Committed |
original Discourse thread: https:/ /discourse. maas.io/ t/maas- cisco-ucs- iscsi/7942