All the listed test cases appear to have been covered and successfully verified for both xenial and yakkety. We're just waiting for Jason to do his testing (he said "tomorrow" Friday December 16...). If that gets done then, the updates should be good to release on Monday (there aren't usually SRU promotions to -updates on Fridays).
** Description changed: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:::::eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: X / Y [+]/[+] MAAS on IPv6-only network [+]/[+] MAAS on IPv4-only network [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) Non-MAAS test cases: X / Y [+]/[+] ip="" and ip6 not present [+]/[+] ip=:::::eth0:dhcp and ip6 not present [+]/[+] d-i install with iSCSI remote root should complete normally - [+]/[ ] Validate normal boot without remote root + [+]/[+] Validate normal boot without remote root [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=) [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=) [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)52-54-00-53-5d-24 [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Committed Status in initramfs-tools source package in Yakkety: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: Fix Committed Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) Bugs related to uploads for this specific SRU: cloud-init: bug 1460715: different fix unrelated to this SRU bug 1639930: ip6= on kernel command line bug 1642679: different fix unrelated to this SRU bug 1644043: different fix unrelated to this SRU ifupdown: bug 1629972: networking.service takes down lo on stop initramfs-tools: bug 1621507: no IPv6 DHCP support in early boot bug 1628306: regression-update (failure when ip="") bug 1631474: regression-update (failure when ip=:::::eth0:dhcp) isc-dhcp: bug 1621507: no IPv6 DHCP support in early boot bug 1633479: dhclient does not wait for IPv6 DAD open-iscsi: bug 1621507: no IPv6 DHCP support in early boot [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. [Stable Fix] These uploads add "ip6=" to the command line syntax to configure ipv6 using the defacto isc-dhcp-client. IPv4 configuration (and "ip=" syntax) remain unchanged. Valid format for the ip6= command line option is: ip6=none (or ip6=off or ip6=) -- do not configure ipv6 ip6=DEVICE -- run IPv6 dhclient on device DEVICE. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. [Tests for verification] Whoever checks the last one off, please mark verification done. MAAS test cases: X / Y [+]/[+] MAAS on IPv6-only network [+]/[+] MAAS on IPv4-only network [+]/[+] MAAS booting IPv4 on dual-stack network (with and without dhcp6) [+]/[+] MAAS booting IPv6 on dual-stack network (with and without dhcp4) Non-MAAS test cases: X / Y [+]/[+] ip="" and ip6 not present [+]/[+] ip=:::::eth0:dhcp and ip6 not present [+]/[+] d-i install with iSCSI remote root should complete normally [+]/[+] Validate normal boot without remote root [+]/[+] Booting an iSCSI remote root via IPv4 (using ip=) [+]/[+] Booting an iSCSI remote root via IPv6 (using ip6=) [+]/[+] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case) [+]/[+] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)52-54-00-53-5d-24 [+]/[+] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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
