| 2016-09-08 14:34:14 |
LaMont Jones |
bug |
|
|
added bug |
| 2016-09-08 14:34:52 |
LaMont Jones |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 |
|
| 2016-09-08 14:34:52 |
LaMont Jones |
bug task added |
|
klibc (Debian) |
|
| 2016-09-08 15:03:14 |
Andres Rodriguez |
bug task added |
|
maas |
|
| 2016-09-08 15:03:20 |
LaMont Jones |
bug task added |
|
initramfs-tools (Ubuntu) |
|
| 2016-09-08 15:03:22 |
Andres Rodriguez |
maas: status |
New |
Confirmed |
|
| 2016-09-08 15:03:23 |
Andres Rodriguez |
maas: importance |
Undecided |
Critical |
|
| 2016-09-08 15:03:29 |
Andres Rodriguez |
tags |
|
maas-ipv6 |
|
| 2016-09-08 15:16:55 |
LaMont Jones |
tags |
maas-ipv6 |
maas-ipv76 |
|
| 2016-09-08 15:17:00 |
LaMont Jones |
tags |
maas-ipv76 |
maas-ipv6 |
|
| 2016-09-08 15:18:52 |
LaMont Jones |
summary |
ipconfig lacks ipv6 support |
initramfs-tools configure_networking() fails to dhcp ipv6 addresses |
|
| 2016-09-08 15:29:14 |
Bug Watch Updater |
klibc (Debian): status |
Unknown |
New |
|
| 2016-09-08 15:34:57 |
Steve Langasek |
initramfs-tools (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-09-08 18:46:08 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): status |
New |
Triaged |
|
| 2016-09-08 18:46:11 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): importance |
Undecided |
High |
|
| 2016-09-09 15:21:06 |
Ryan Harper |
bug |
|
|
added subscriber Ryan Harper |
| 2016-09-14 21:01:46 |
Mathieu Trudel-Lapierre |
bug task added |
|
isc-dhcp (Ubuntu) |
|
| 2016-09-14 21:01:57 |
Mathieu Trudel-Lapierre |
isc-dhcp (Ubuntu): status |
New |
In Progress |
|
| 2016-09-14 21:01:59 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-09-14 21:02:02 |
Mathieu Trudel-Lapierre |
isc-dhcp (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-09-14 21:02:04 |
Mathieu Trudel-Lapierre |
isc-dhcp (Ubuntu): importance |
Undecided |
High |
|
| 2016-09-20 21:41:33 |
LaMont Jones |
bug task added |
|
iproute2 (Ubuntu) |
|
| 2016-09-20 21:41:48 |
LaMont Jones |
bug task added |
|
open-iscsi (Ubuntu) |
|
| 2016-09-20 21:44:34 |
LaMont Jones |
open-iscsi (Ubuntu): assignee |
|
LaMont Jones (lamont) |
|
| 2016-09-20 21:44:49 |
LaMont Jones |
iproute2 (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-09-20 21:53:24 |
LaMont Jones |
open-iscsi (Ubuntu): status |
New |
Fix Committed |
|
| 2016-09-20 21:53:41 |
LaMont Jones |
open-iscsi (Ubuntu): milestone |
|
ubuntu-16.10 |
|
| 2016-09-20 21:53:51 |
LaMont Jones |
open-iscsi (Ubuntu): milestone |
ubuntu-16.10 |
|
|
| 2016-09-20 21:54:00 |
LaMont Jones |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-09-20 21:54:00 |
LaMont Jones |
bug task added |
|
initramfs-tools (Ubuntu Xenial) |
|
| 2016-09-20 21:54:00 |
LaMont Jones |
bug task added |
|
klibc (Ubuntu Xenial) |
|
| 2016-09-20 21:54:00 |
LaMont Jones |
bug task added |
|
open-iscsi (Ubuntu Xenial) |
|
| 2016-09-20 21:54:00 |
LaMont Jones |
bug task added |
|
isc-dhcp (Ubuntu Xenial) |
|
| 2016-09-20 21:54:00 |
LaMont Jones |
bug task added |
|
iproute2 (Ubuntu Xenial) |
|
| 2016-09-21 14:18:45 |
Scott Moser |
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
Anyone wanting to netboot in an ipv6-only environment is affected. |
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
Anyone wanting to netboot in an ipv6-only environment is affected.
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init |
|
| 2016-09-21 14:48:07 |
LaMont Jones |
bug task deleted |
iproute2 (Ubuntu) |
|
|
| 2016-09-21 14:50:45 |
LaMont Jones |
bug task deleted |
iproute2 (Ubuntu Xenial) |
|
|
| 2016-09-24 01:16:12 |
Steve Langasek |
isc-dhcp (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-09-24 01:16:19 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-24 01:16:24 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-24 01:16:30 |
Steve Langasek |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2016-09-24 01:21:49 |
LaMont Jones |
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
Anyone wanting to netboot in an ipv6-only environment is affected.
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init |
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
[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.
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.
[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. |
|
| 2016-09-24 01:43:35 |
Steve Langasek |
initramfs-tools (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-09-24 01:46:21 |
Steve Langasek |
open-iscsi (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-09-24 19:11:14 |
Mathew Hodson |
initramfs-tools (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-09-24 19:11:54 |
Mathew Hodson |
isc-dhcp (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-09-24 19:12:26 |
Mathew Hodson |
open-iscsi (Ubuntu): importance |
Undecided |
High |
|
| 2016-09-24 19:12:40 |
Mathew Hodson |
open-iscsi (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-09-26 13:55:14 |
Gavin Panella |
maas: status |
Confirmed |
Triaged |
|
| 2016-09-26 20:42:28 |
Launchpad Janitor |
isc-dhcp (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-09-27 08:18:29 |
Launchpad Janitor |
klibc (Ubuntu): status |
New |
Confirmed |
|
| 2016-09-27 08:18:29 |
Launchpad Janitor |
klibc (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-09-28 09:18:36 |
Launchpad Janitor |
isc-dhcp (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-09-29 08:37:15 |
Launchpad Janitor |
initramfs-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-10-03 16:54:21 |
LaMont Jones |
bug task added |
|
ifupdown (Ubuntu) |
|
| 2016-10-03 17:14:30 |
LaMont Jones |
open-iscsi (Ubuntu): assignee |
LaMont Jones (lamont) |
|
|
| 2016-10-03 18:39:11 |
LaMont Jones |
bug task deleted |
ifupdown (Ubuntu) |
|
|
| 2016-10-03 18:39:23 |
LaMont Jones |
bug task deleted |
ifupdown (Ubuntu Xenial) |
|
|
| 2016-10-06 00:54:20 |
Mike Pontillo |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2016-10-06 04:29:04 |
Launchpad Janitor |
initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-06 04:38:02 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-10-06 04:38:08 |
Launchpad Janitor |
open-iscsi (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-06 04:46:59 |
Launchpad Janitor |
open-iscsi (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2016-10-06 15:16:29 |
LaMont Jones |
klibc (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2016-10-06 15:17:12 |
LaMont Jones |
klibc (Ubuntu Xenial): status |
Confirmed |
Won't Fix |
|
| 2016-10-06 15:17:23 |
Andres Rodriguez |
maas: status |
Triaged |
Fix Released |
|
| 2016-10-11 17:32:44 |
LaMont Jones |
tags |
maas-ipv6 verification-done |
maas-ipv6 verification-pending |
|
| 2016-10-12 17:48:27 |
LaMont Jones |
tags |
maas-ipv6 verification-pending |
maas-ipv6 verification-failed |
|
| 2016-10-17 18:10:29 |
Steve Langasek |
initramfs-tools (Ubuntu Xenial): status |
Fix Released |
Triaged |
|
| 2016-10-17 18:10:44 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-10-17 18:18:14 |
Steve Langasek |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-10-17 18:18:14 |
Steve Langasek |
bug task added |
|
initramfs-tools (Ubuntu Yakkety) |
|
| 2016-10-17 18:18:14 |
Steve Langasek |
bug task added |
|
klibc (Ubuntu Yakkety) |
|
| 2016-10-17 18:18:14 |
Steve Langasek |
bug task added |
|
open-iscsi (Ubuntu Yakkety) |
|
| 2016-10-17 18:18:14 |
Steve Langasek |
bug task added |
|
isc-dhcp (Ubuntu Yakkety) |
|
| 2016-10-24 17:16:54 |
Scott Moser |
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
[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.
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.
[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. |
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)
[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.
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.
[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. |
|
| 2016-10-27 21:00:05 |
LaMont Jones |
maas: status |
Fix Released |
In Progress |
|
| 2016-10-27 21:00:05 |
LaMont Jones |
maas: assignee |
|
LaMont Jones (lamont) |
|
| 2016-10-27 21:01:31 |
Launchpad Janitor |
branch linked |
|
lp:~lamont/maas/bug-1621507 |
|
| 2016-10-30 13:50:40 |
Launchpad Janitor |
initramfs-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-11-02 01:40:10 |
LaMont Jones |
attachment added |
|
debdiff for initramfs-tools https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770859/+files/initramfs-tools.debdiff |
|
| 2016-11-02 01:40:41 |
LaMont Jones |
attachment added |
|
open-iscsi debdiff https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770860/+files/open-iscsi.debdiff |
|
| 2016-11-02 01:41:05 |
LaMont Jones |
attachment added |
|
isc-dhcp debdiff https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4770861/+files/isc-dhcp.debdiff |
|
| 2016-11-02 01:41:47 |
LaMont Jones |
initramfs-tools (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:42:40 |
LaMont Jones |
isc-dhcp (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:42:58 |
LaMont Jones |
isc-dhcp (Ubuntu Xenial): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:46:38 |
LaMont Jones |
isc-dhcp (Ubuntu Yakkety): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:49:36 |
LaMont Jones |
open-iscsi (Ubuntu): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:54:06 |
LaMont Jones |
open-iscsi (Ubuntu Xenial): status |
Fix Released |
In Progress |
|
| 2016-11-02 01:56:03 |
LaMont Jones |
open-iscsi (Ubuntu Yakkety): status |
Fix Released |
In Progress |
|
| 2016-11-02 04:29:15 |
Ubuntu Foundations Team Bug Bot |
tags |
maas-ipv6 verification-failed |
maas-ipv6 patch verification-failed |
|
| 2016-11-02 14:08:41 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
| 2016-11-09 00:44:13 |
Scott Moser |
attachment added |
|
suggested further changes https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507/+attachment/4774679/+files/out.diff |
|
| 2016-11-09 15:57:15 |
Robie Basak |
open-iscsi (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-11-09 15:57:17 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-11-09 15:57:23 |
Robie Basak |
tags |
maas-ipv6 patch verification-failed |
maas-ipv6 patch |
|
| 2016-11-09 15:57:24 |
Robie Basak |
tags |
maas-ipv6 patch |
maas-ipv6 patch verification-needed |
|
| 2016-11-09 15:59:01 |
Robie Basak |
open-iscsi (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-11-15 17:23:52 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-11-15 17:24:54 |
Mathieu Trudel-Lapierre |
isc-dhcp (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-11-22 02:38:32 |
LaMont Jones |
tags |
maas-ipv6 patch verification-needed |
maas-ipv6 patch verification-done |
|
| 2016-11-23 10:00:20 |
Launchpad Janitor |
open-iscsi (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-11-23 10:00:37 |
Launchpad Janitor |
open-iscsi (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-11-29 23:00:49 |
Chris Halse Rogers |
initramfs-tools (Ubuntu Xenial): status |
Triaged |
Fix Committed |
|
| 2016-11-29 23:00:51 |
Chris Halse Rogers |
isc-dhcp (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-11-29 23:01:04 |
Chris Halse Rogers |
tags |
maas-ipv6 patch verification-done |
maas-ipv6 patch |
|
| 2016-11-29 23:01:06 |
Chris Halse Rogers |
tags |
maas-ipv6 patch |
maas-ipv6 patch verification-needed |
|
| 2016-11-29 23:26:28 |
Chris Halse Rogers |
initramfs-tools (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-11-29 23:26:30 |
Chris Halse Rogers |
isc-dhcp (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-12-07 15:26:56 |
LaMont Jones |
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)
[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.
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.
[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. |
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)
[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.
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. |
|
| 2016-12-08 13:03:54 |
Robie Basak |
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)
[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.
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. |
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)
[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. |
|
| 2016-12-09 09:19:13 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~cyphermox/ubuntu/+source/isc-dhcp/+git/isc-dhcp/+merge/312891 |
|
| 2016-12-09 10:49:58 |
LaMont Jones |
merge proposal linked |
|
https://code.launchpad.net/~lamont/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/312899 |
|
| 2016-12-09 13:06:31 |
Robie Basak |
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)
[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. |
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. |
|
| 2016-12-09 15:32:26 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2016-12-09 18:26:59 |
Robie Basak |
open-iscsi (Ubuntu Xenial): status |
Fix Released |
In Progress |
|
| 2016-12-09 18:28:09 |
Robie Basak |
open-iscsi (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-12-09 18:28:32 |
Robie Basak |
open-iscsi (Ubuntu Xenial): status |
Fix Committed |
In Progress |
|
| 2016-12-09 18:28:46 |
Robie Basak |
open-iscsi (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-12-13 16:06:37 |
LaMont Jones |
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. |
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:
[ ] MAAS on IPv6-only network
[ ] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] .... |
|
| 2016-12-14 00:35:03 |
Mathieu Trudel-Lapierre |
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:
[ ] MAAS on IPv6-only network
[ ] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] .... |
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:
[ ] MAAS on IPv6-only network
[ ] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
|
| 2016-12-14 15:31:32 |
LaMont Jones |
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:
[ ] MAAS on IPv6-only network
[ ] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
|
| 2016-12-14 22:16:07 |
LaMont Jones |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[ ] MAAS booting IPv4 on dual-stack network
[ ] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
|
| 2016-12-14 22:18:27 |
LaMont Jones |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
|
| 2016-12-15 14:23:52 |
Mathieu Trudel-Lapierre |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only)
[ ] jderose's use cases |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 14:31:42 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Jason Gerard DeRose |
| 2016-12-15 14:55:17 |
LaMont Jones |
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:
[+] MAAS on IPv6-only network
[+] MAAS on IPv4-only network
[+] MAAS booting IPv4 on dual-stack network
[+] MAAS booting IPv6 on dual-stack network
Non-MAAS test cases:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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:
[+] 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:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 20:09:28 |
Brian Murray |
open-iscsi (Ubuntu Yakkety): status |
Fix Released |
Fix Committed |
|
| 2016-12-15 20:11:06 |
Mathieu Trudel-Lapierre |
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:
[+] 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:
[ ] 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 via IPv6 (no ip6=, d-i use case)
[ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting device)
[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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:
[+] 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)
[ ]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 20:18:12 |
Mathieu Trudel-Lapierre |
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:
[+] 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)
[ ]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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:
[+] 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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 22:19:36 |
Mathieu Trudel-Lapierre |
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:
[+] 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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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:
[+] 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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 22:26:25 |
LaMont Jones |
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:
[+] 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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
|
| 2016-12-15 23:34:01 |
Mathieu Trudel-Lapierre |
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)
[+]/[ ] Booting an iSCSI remote root on mixed network with no options (IPv4 should be used only) |
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) |
|
| 2016-12-16 01:09:33 |
Mathieu Trudel-Lapierre |
isc-dhcp (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-12-16 01:10:07 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Xenial): milestone |
|
xenial-updates |
|
| 2016-12-16 01:10:07 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-12-16 03:03:15 |
Mathieu Trudel-Lapierre |
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) |
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) |
|
| 2016-12-16 16:12:15 |
LaMont Jones |
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) |
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) |
|
| 2016-12-16 18:04:29 |
LaMont Jones |
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) |
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) |
|
| 2016-12-16 18:09:42 |
LaMont Jones |
tags |
maas-ipv6 patch verification-needed |
maas-ipv6 patch verification-done |
|
| 2016-12-19 16:27:26 |
Launchpad Janitor |
open-iscsi (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-19 16:27:31 |
Launchpad Janitor |
isc-dhcp (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-19 16:27:35 |
Launchpad Janitor |
initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-01-12 17:28:43 |
Launchpad Janitor |
open-iscsi (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-01-12 17:56:53 |
marcojjm |
bug |
|
|
added subscriber marcojjm |
| 2017-01-12 17:57:09 |
marcojjm |
removed subscriber marcojjm |
|
|
|
| 2017-01-19 14:22:39 |
Launchpad Janitor |
isc-dhcp (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-01-19 14:25:09 |
Launchpad Janitor |
initramfs-tools (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-01-27 22:34:02 |
Launchpad Janitor |
open-iscsi (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-03-15 09:09:31 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
| 2017-12-29 07:40:33 |
Bug Watch Updater |
klibc (Debian): status |
New |
Confirmed |
|
| 2018-03-09 08:02:41 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203 |
|
| 2018-03-09 08:25:23 |
Launchpad Janitor |
merge proposal unlinked |
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/341203 |
|
|
