| 2016-09-08 20:15:35 |
LaMont Jones |
bug |
|
|
added bug |
| 2016-09-08 21:35:03 |
Andres Rodriguez |
bug task added |
|
maas |
|
| 2016-09-08 21:35:51 |
Andres Rodriguez |
tags |
|
maas-ipv6 |
|
| 2016-09-08 21:39:07 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2016-09-09 15:20:38 |
Ryan Harper |
bug |
|
|
added subscriber Ryan Harper |
| 2016-09-19 23:00:15 |
LaMont Jones |
attachment added |
|
A patch that does not fix the problem. https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743947/+files/ipv6-config |
|
| 2016-09-19 23:01:32 |
LaMont Jones |
attachment added |
|
net-eno1.conf from the booted system https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743948/+files/net-eno1.conf |
|
| 2016-09-19 23:02:04 |
LaMont Jones |
attachment added |
|
cloud-init.log https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743949/+files/cloud-init.log |
|
| 2016-09-19 23:03:03 |
LaMont Jones |
attachment added |
|
cloud-init-output.log from the system https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1621615/+attachment/4743950/+files/cloud-init-output.log |
|
| 2016-09-19 23:03:55 |
LaMont Jones |
maas: milestone |
|
2.1.0 |
|
| 2016-09-20 21:38:53 |
LaMont Jones |
bug task added |
|
open-iscsi (Ubuntu) |
|
| 2016-09-20 21:39:27 |
LaMont Jones |
open-iscsi (Ubuntu): status |
New |
Invalid |
|
| 2016-09-20 21:39:55 |
LaMont Jones |
affects |
open-iscsi (Ubuntu) |
ubuntu |
|
| 2016-09-20 21:40:35 |
LaMont Jones |
bug task deleted |
ubuntu |
|
|
| 2016-09-21 14:16:09 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
| 2016-09-21 14:16:09 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-09-21 14:18:16 |
Scott Moser |
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. |
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 |
|
| 2016-09-21 14:37:17 |
Scott Moser |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/306345 |
|
| 2016-09-21 14:38:20 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-09-21 15:41:57 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2016-09-21 15:41:57 |
Scott Moser |
cloud-init: status |
New |
In Progress |
|
| 2016-09-24 05:28:43 |
Steve Langasek |
cloud-init (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-09-24 05:28:45 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-24 05:28:51 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-24 05:28:57 |
Steve Langasek |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2016-09-24 14:15:40 |
LaMont Jones |
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 |
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...) |
|
| 2016-09-24 19:16:19 |
Mathew Hodson |
cloud-init (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-09-27 22:45:40 |
LaMont Jones |
bug task added |
|
cloud-initramfs-tools (Ubuntu) |
|
| 2016-09-27 22:46:28 |
LaMont Jones |
bug task deleted |
cloud-initramfs-tools (Ubuntu) |
|
|
| 2016-09-28 09:15:50 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-09-28 14:16:02 |
Launchpad Janitor |
branch linked |
|
lp:cloud-initramfs-tools |
|
| 2016-09-29 17:57:42 |
Brian Murray |
bug task added |
|
cloud-initramfs-tools (Ubuntu) |
|
| 2016-09-29 17:59:34 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2016-10-02 03:27:47 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu): status |
New |
Fix Released |
|
| 2016-10-02 18:47:56 |
Stéphane Graber |
cloud-initramfs-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-10-02 23:00:28 |
Mathew Hodson |
cloud-initramfs-tools (Ubuntu): importance |
Undecided |
High |
|
| 2016-10-02 23:00:31 |
Mathew Hodson |
cloud-initramfs-tools (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-10-03 16:29:10 |
Scott Moser |
cloud-init: status |
In Progress |
Fix Committed |
|
| 2016-10-04 18:11:03 |
Launchpad Janitor |
branch linked |
|
lp:~lamont/cloud-initramfs-tools/0.29ubuntu3 |
|
| 2016-10-04 20:15:51 |
Launchpad Janitor |
branch linked |
|
lp:~lamont/cloud-initramfs-tools/yakkety-ipv6 |
|
| 2016-10-06 02:54:49 |
LaMont Jones |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2016-10-06 15:19:23 |
Andres Rodriguez |
maas: status |
New |
Fix Released |
|
| 2016-10-07 14:48:30 |
Blake Rouse |
maas: assignee |
|
LaMont Jones (lamont) |
|
| 2016-10-12 08:31:12 |
Martin Pitt |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-10-12 08:31:17 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-12 08:34:48 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-24 17:16:16 |
Scott Moser |
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...) |
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
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
[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...) |
|
| 2016-11-01 04:00:56 |
LaMont Jones |
merge proposal linked |
|
https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718 |
|
| 2016-11-01 04:05:52 |
Launchpad Janitor |
branch linked |
|
lp:~lamont/cloud-initramfs-tools/bug-1621615-device6 |
|
| 2016-11-02 02:28:32 |
LaMont Jones |
maas: status |
Fix Released |
In Progress |
|
| 2016-11-02 02:28:45 |
LaMont Jones |
cloud-init: status |
Fix Committed |
Confirmed |
|
| 2016-11-02 02:28:53 |
LaMont Jones |
cloud-init (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2016-11-02 02:29:00 |
LaMont Jones |
cloud-init (Ubuntu Xenial): status |
Fix Released |
Confirmed |
|
| 2016-11-02 02:29:06 |
LaMont Jones |
cloud-initramfs-tools (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2016-11-02 02:29:11 |
LaMont Jones |
cloud-initramfs-tools (Ubuntu Xenial): status |
Fix Released |
Confirmed |
|
| 2016-11-02 02:29:22 |
LaMont Jones |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-11-02 02:29:22 |
LaMont Jones |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2016-11-02 02:29:22 |
LaMont Jones |
bug task added |
|
cloud-initramfs-tools (Ubuntu Yakkety) |
|
| 2016-11-02 02:31:35 |
LaMont Jones |
maas: milestone |
2.1.0 |
2.1.1 |
|
| 2016-11-03 03:10:58 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-11-03 14:00:35 |
Scott Moser |
cloud-init: status |
Confirmed |
Fix Committed |
|
| 2016-11-03 14:00:40 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2016-11-03 14:00:44 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-11-03 14:00:51 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2016-11-03 14:00:54 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-11-04 14:32:34 |
Blake Rouse |
maas: milestone |
2.1.1 |
2.1.2 |
|
| 2016-11-07 19:59:13 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-11-14 19:37:25 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/cloud-initramfs-tools/pkg |
|
| 2016-11-15 23:30:53 |
Steve Langasek |
cloud-init (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2016-11-15 23:30:56 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-15 23:31:05 |
Steve Langasek |
tags |
maas-ipv6 verification-done |
maas-ipv6 |
|
| 2016-11-15 23:31:06 |
Steve Langasek |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2016-11-22 02:12:39 |
Scott Moser |
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
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
[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...) |
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
* 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://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...) |
|
| 2016-11-22 02:29:39 |
Scott Moser |
attachment added |
|
ipv6-cmdline-net.diff: changes and description of changes https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1621615/+attachment/4781308/+files/ipv6-cmdline-net.diff |
|
| 2016-11-22 02:30:08 |
Scott Moser |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done-xenial-cloud-init |
|
| 2016-11-23 13:52:46 |
Andres Rodriguez |
maas: milestone |
2.1.2 |
2.1.3 |
|
| 2016-11-24 20:00:36 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-11-29 01:32:39 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2016-11-29 01:32:42 |
Scott Moser |
cloud-initramfs-tools (Ubuntu Yakkety): status |
Confirmed |
In Progress |
|
| 2016-11-29 23:13:13 |
Chris Halse Rogers |
cloud-initramfs-tools (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-11-29 23:13:27 |
Chris Halse Rogers |
tags |
maas-ipv6 verification-done-xenial-cloud-init |
maas-ipv6 verification-done-xenial-cloud-init verification-needed |
|
| 2016-11-29 23:41:49 |
Chris Halse Rogers |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2016-11-29 23:49:21 |
Chris Halse Rogers |
cloud-initramfs-tools (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-12-16 18:30:38 |
LaMont Jones |
tags |
maas-ipv6 verification-done-xenial-cloud-init verification-needed |
maas-ipv6 verification-done verification-done-xenial-cloud-init |
|
| 2016-12-19 16:28:07 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-21 01:05:10 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-12-21 01:06:15 |
Launchpad Janitor |
cloud-initramfs-tools (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-12-23 17:39:18 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2018-03-05 10:53:27 |
Blake Rouse |
maas: status |
In Progress |
Invalid |
|
| 2018-03-05 10:53:30 |
Blake Rouse |
maas: assignee |
LaMont Jones (lamont) |
|
|
| 2018-03-05 10:53:32 |
Blake Rouse |
maas: milestone |
2.1.3 |
|
|
| 2023-05-10 16:29:29 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2724 |
|
