network not configured when ipv6 netbooted into cloud-init
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
cloud-initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned |
Bug Description
https:/
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_
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
* bug 1639930: initramfs network configuration ignored if only ip6= on kernel command line
[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:/
[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...)
Related branches
- cloud-initramfs-tools: Pending requested
-
Diff: 172 lines (+89/-26)2 files modifieddebian/changelog (+1/-1)
dyn-netconf/scripts/init-bottom/cloud-initramfs-dyn-netconf (+88/-25)
- cloud-initramfs-tools: Pending requested
-
Diff: 33 lines (+8/-4)1 file modifieddyn-netconf/scripts/init-bottom/cloud-initramfs-dyn-netconf (+8/-4)
- cloud-init Commiters: Pending requested
-
Diff: 21 lines (+4/-3)1 file modifiedcloudinit/net/cmdline.py (+4/-3)
- cloud-init Commiters: Pending requested
-
Diff: 104 lines (+53/-5)2 files modifiedcloudinit/net/cmdline.py (+10/-5)
tests/unittests/test_net.py (+43/-0)
tags: | added: maas-ipv6 |
Changed in open-iscsi (Ubuntu): | |
status: | New → Invalid |
affects: | open-iscsi (Ubuntu) → ubuntu |
no longer affects: | ubuntu |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
description: | updated |
Changed in cloud-init: | |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
Changed in cloud-init (Ubuntu Xenial): | |
importance: | Undecided → High |
no longer affects: | cloud-initramfs-tools (Ubuntu) |
Changed in cloud-initramfs-tools (Ubuntu): | |
importance: | Undecided → High |
Changed in cloud-initramfs-tools (Ubuntu Xenial): | |
importance: | Undecided → High |
Changed in cloud-init: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | New → Fix Released |
Changed in maas: | |
assignee: | nobody → LaMont Jones (lamont) |
description: | updated |
Changed in cloud-init: | |
status: | Confirmed → Fix Committed |
Changed in cloud-init (Ubuntu Yakkety): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cloud-initramfs-tools (Ubuntu Yakkety): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
description: | updated |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
Changed in cloud-initramfs-tools (Ubuntu Xenial): | |
status: | Confirmed → In Progress |
Changed in cloud-initramfs-tools (Ubuntu Yakkety): | |
status: | Confirmed → In Progress |
Changed in maas: | |
status: | In Progress → Invalid |
assignee: | LaMont Jones (lamont) → nobody |
milestone: | 2.1.3 → none |
With the attached patch applied to0.7.8- 1-g3705bb5- 0ubuntu1~ 16.04.1, we still fail.
Details of the failure are attached below.