[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
** Tags added: regression-update -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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. [Regressions] bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option -- 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
Sorry for not linking the bug here initially, that's my fault and I apologize... -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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. [Regressions] bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option -- 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
** Description changed: [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. + + [Regressions] + bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option -- 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. -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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. [Regressions] bug 1631474: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option -- 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
Regression tracked via bug #1631474 -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
(found bug 1631474) -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
lscotte, did you open a bug? -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
initramfs-tools 0.122ubuntu8.3 has resulted in a serious regression for instances running in AWS when the ip=dhcp boot option set. 0.122ubuntu8.2 (and previous versions) do not exhibit the problem. I'll create a new issue for tracking, but wanted to add a comment here. -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.3 --- initramfs-tools (0.122ubuntu8.3) xenial; urgency=medium * scripts/functions: make sure we can try to start all available and suitable interfaces if ip= isn't set when setting up the network, and exit as soon as we get an IP address. This retains the old behavior from ipconfig when ip= is unset, for really simple remote-root scenarios. (LP: #1628306) * scripts/functions: retain bootp/rarp behavior using ipconfig. -- Mathieu Trudel-Lapierre Tue, 27 Sep 2016 16:27:38 -0400 ** Changed in: initramfs-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
System boots correctly with the new initramfs-tools. Verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
This bug was fixed in the package initramfs-tools - 0.125ubuntu5 --- initramfs-tools (0.125ubuntu5) yakkety; urgency=medium * scripts/functions: make sure we can try to start all available and suitable interfaces if ip= isn't set when setting up the network, and exit as soon as we get an IP address. This retains the old behavior from ipconfig when ip= is unset, for really simple remote-root scenarios. (LP: #1628306) -- Mathieu Trudel-Lapierre Tue, 27 Sep 2016 18:25:50 -0400 ** Changed in: initramfs-tools (Ubuntu Yakkety) Status: In Progress => Fix Released -- 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: Fix Released Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Released 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
[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set
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