Attached the uploaded diff for jammy. Besides the few lines changed in
scripts/functions I backported the improvements of the autopkgtest to
increase the test coverage and to test on all architectures. See
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+ref/ubuntu/jammy for the individual commits
for details. I tested the autopkgtest changes in my PPA.
** Description changed:
+ [ 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-$DEVICE.conf file for the iscsi interface.
The existence of this file makes configure_networking() skip configuring
the BOOTIF later due to this code in `scripts/functions`:
- for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
- if [ -e "$x" ]; then
- IP=done
- break
- fi
- done
+ for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
+ if [ -e "$x" ]; then
+ IP=done
+ break
+ fi
+ done
** Patch added: "initramfs-tools_0.140ubuntu13.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+attachment/5756863/+files/initramfs-tools_0.140ubuntu13.5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Jammy:
New
Status in open-iscsi source package in Jammy:
New
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-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
