This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.3
---------------
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.3) xenial-proposed; urgency=medium
* ntp: move to run after apt configuration (LP: #1628337).
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.2) xenial; urgency=medium
* Support IPv6 config coming from initramfs. LP: #1621615.
-- Scott Moser <smo...@ubuntu.com> Mon, 03 Oct 2016 12:22:26 -0400
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
Status in cloud-init:
Fix Committed
Status in MAAS:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-initramfs-tools source package in Xenial:
Fix Released
Bug description:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
MAAS.
After I hand-walked busybox through getting an IPv6 address,
everything worked just fine until cloud-init couldn't fetch the
instance data, because it insisted on bringing up the interface in
IPv4, and there is no IPv4 DHCP on that vlan.
Please work with initramfs and friends on getting IPv6 netboot to
actually configure the interface. This may be as simple as teaching
it about "inet6 dhcp" interfaces, and bolting the pieces together.
Note that "use radvd" is not really an option for our use case.
Related bugs:
* bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6
addresses
[Impact]
It is not possible to enlist, commmission, or deploy with MAAS in an
IPv6-only environment. Anyone wanting to netboot with a network root
filesystem in an IPv6-only environment is affected.
This upload addresses this by accepting, using, and forwarding any
IPV6* variables from the initramfs boot. (See
https://launchpad.net/bugs/1621507)
[Test Case]
See Bug 1229458. Configure radvd, dhcpd, and tftpd for your IPv6-only
netbooting world. Pass the boot process an IPv6 address to fetch
instance-data from, and see it fail to configure the network.
[Regression Potential]
1) If the booting host is in a dual-boot environment, and the
instance-dat URL uses a hostname that has both A and AAAA RRsets, the
booting host may try to talk IPv6 to get instance data. If the
instance-data providing host is only allowing that to happen over
IPv4, it will fail. (It also represents a configuraiton issue on the
providing host...)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
