Hello Mathieu, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: initramfs-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1628306 Title: network booting fails for iscsi root if no ip is set Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: In Progress Bug description: [Impact] Remote-root installs (eg. / over iscsi and similar) where the configuration is simple, and no extra parameters are included on the kernel command-line (as opposed to MaaS specifying everything). [Test case] 1) do an installation with /boot on a local disk and / and swap over a remote LUN (iSCSI is simple to do). 2) Update to initramfs-tools with isc-dhcp support. [Regression potential] This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root filesystem would constitue a regression. -- I did a new install with /boot on /dev/sda, and everything else (/ and swap) on an iSCSI LUN. Booting this with initramfs-tools using ipconfig works without issues. Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial) fails because no interface is specified. This appears to be because ipconfig interprets "" as meaning to try every interface until one works (or all fail), whereas calling dhclient without an interface name simply returns a failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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
