Reopening, as we reverted the SRU (but will also fix things in Zesty and
Yakkety with a better method than overriding ip=)
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Status in MAAS:
Status in initramfs-tools package in Ubuntu:
Status in isc-dhcp package in Ubuntu:
Status in klibc package in Ubuntu:
Status in open-iscsi package in Ubuntu:
Status in initramfs-tools source package in Xenial:
Status in isc-dhcp source package in Xenial:
Status in klibc source package in Xenial:
Status in open-iscsi source package in Xenial:
Status in initramfs-tools source package in Yakkety:
Status in isc-dhcp source package in Yakkety:
Status in klibc source package in Yakkety:
Status in open-iscsi source package in Yakkety:
Status in klibc package in Debian:
initramfs' configure_networking function uses ipconfig to configure the
ipconfig does not support dhcpv6. See:
* bug 1229458: grub2 needed changes
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
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.
These uploads address this by replacing the one-off klibc dhcp client
(IPv4-only) with the defacto standard isc-dhcp-client, and thereby
provide both ipv6 and ipv4 DHCP configuration.
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.
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.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp