[Bug 2091904] Re: IPv6 iBFT boot runs into a timeout

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.145ubuntu2

---------------
initramfs-tools (0.145ubuntu2) plucky; urgency=medium

  * Fix shellcheck complaints in debian/tests
  * configure_networking: Configure IPv4 or IPv6 based on iBFT IP address
    (LP: #2091904)
  * test:
    - support setting a disk label in build_fs_ext2
    - test-common: move disc logic out of _run_qemu
    - move wait_for_server_startup to test-common
    - check for QEMU PID in wait_for_server_startup
    - Add qemu-net-iscsi autopkgtest for iBFT test cases

 -- Benjamin Drung <bdrung at ubuntu.com>  Thu, 06 Feb 2025 22:21:42 +0100

** Changed in: initramfs-tools (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2091904

Title:
  IPv6 iBFT boot runs into a timeout

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in open-iscsi package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Noble:
  New
Status in open-iscsi source package in Noble:
  New
Status in initramfs-tools source package in Oracular:
  New
Status in open-iscsi source package in Oracular:
  New

Bug description:
  iSCSI Boot Firmware Table (iBFT) can provide the network configuration
  that is needed to boot over iSCSI. The iBFT can contain IPv4 or IPv6
  addresses. local-top/iscsi calls `configure_networking`. The default
  behaviour of `configure_networking` is DHCPv4 on all available
  interfaces (if ip= and ip6= are not set). If iBFT provides IPv6
  addresses and no DHCPv4 server are running, `configure_networking`
  will only try DHCPv4 and run into a timeout.

  Placing the single line "ISCSI_AUTO=true" into
  /etc/iscsi/iscsi.initramfs, or use the kernel boot line option
  "iscsi_auto" will configure the network devices based on iBFT, but the
  code in `local-top/iscsi` will assume that the addresses are IPv4.

  dracut on the other hand has the kernel boot line parameters
  `rd.iscsi.firmware=1` and `rd.iscsi.ibft` and `ibft` as option for the
  `ip` parameter. The `ibft` option is a bit under documented.
  https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/installation_guide/chap-
  anaconda-boot-options mentions `ip=ibft` and dracut.cmdline mentions
  it.

  There are multiple ways to address the timeout with IPv6 iBFT:

  1) Extend `local-top/iscsi` to differentiate between IPv4 and IPv6
  when "iscsi_auto" is used. This information needs to be passed to
  `configure_networking` to only try to bring up that device and
  protocol.

  2) Use `ip=ibft` as indicator to use ibft as source for the network
  configuration. If no ip= parameter is set, local-top/iscsi should
  default to ip=ibft when calling configure_networking.

  Both solutions require passing data to configure_networking.

  Requiring the user to set `ip=off ip6=on` is not a good user
  experience and not a solution in my opinion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2091904/+subscriptions