Canonical produced cloud-images, by default, do not boot with an initrd,
and this is true on Azure as well. the hang occurs late in the startup,
post-cloud-init configuring networking. there are also a bunch of kernel
workers blocked for > 120 seconds, which points to something other than
this package.
[[0;32m OK [0m] Finished [0;1;39mWait for Network to be
Configured[0m.
[ 243.166791] INFO: task kworker/u4:0:9 blocked for more than 120 seconds.
(etc, a bunch more)
For CVM images, they use a unified kernel image (UKI). I don't believe
`initramfs-tools` is a part of the UKI loading. initramfs-tools is
included by unused (and there are movements to remove it from the UKI).
If this is not reproducible with only this package installed, we
shouldn't block the SRU
--
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 Released
Status in open-iscsi package in Ubuntu:
Invalid
Status in initramfs-tools source package in Focal:
Fix Committed
Status in open-iscsi source package in Focal:
New
Status in initramfs-tools source package in Jammy:
Fix Committed
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
