| 2016-11-07 20:14:10 |
Scott Moser |
bug |
|
|
added bug |
| 2016-11-07 20:14:24 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2016-11-07 20:14:29 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2016-11-07 20:17:17 |
Scott Moser |
summary |
initramfs kernel configuration ignored if only ip6= on kernel command line |
initramfs network configuration ignored if only ip6= on kernel command line |
|
| 2016-11-07 20:17:26 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2016-11-07 20:17:37 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-11-07 20:17:37 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-11-07 22:28:41 |
LaMont Jones |
bug task added |
|
maas |
|
| 2016-11-07 22:28:53 |
LaMont Jones |
tags |
|
maas-ipv6 |
|
| 2016-11-07 22:47:49 |
Andres Rodriguez |
maas: milestone |
|
2.1.2 |
|
| 2016-11-09 02:03:36 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/310390 |
|
| 2016-11-23 13:51:14 |
Andres Rodriguez |
maas: milestone |
2.1.2 |
2.1.3 |
|
| 2016-11-28 22:27:29 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-12-02 02:25:37 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-12-02 02:25:37 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2016-12-02 02:25:37 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-12-02 02:25:37 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2016-12-02 02:26:04 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-12-02 02:26:09 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2016-12-02 02:26:11 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2016-12-02 02:26:13 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2016-12-02 02:26:15 |
Scott Moser |
cloud-init (Ubuntu Xenial): assignee |
|
Scott Moser (smoser) |
|
| 2016-12-02 16:12:49 |
Scott Moser |
description |
In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='.
The code currently will return with no network configuration found if there is only ip6=...
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) |
http://pad.lv/1639930
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1639930
=== Begin SRU Template ===
[Impact]
On a system booted with both ip6= and ip= on the kernel command line
cloud-init will raise an exception and fail to process user-data and
have its normal affect on boot.
That is because cloud-init previously raised an exception when more
than one file in /run/net*.conf declared the same DEVICE. Changes to
isc-dhcp and initramfs-tools have changed their behavior and cloud-init
has to adjust to allow DEVICE6= and DEVICE= in separate files.
[Test Case]
Boot a system on a network with both ipv4 and ipv6 dhcp servers,
and pass kernel command line with:
ip=dhcp ip6=dhcp
[Regression Potential]
Regression seems unlikely as this is relaxing a check. Where previously
an exception would have been raised, cloud-init will now go on.
So it seems most likely, something that didn't work before (due to raised
exception) would now still not work, but with failures. That is not
expected, but that would likely be where regressions were found.
=== End SRU Template ===
In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='.
The code currently will return with no network configuration found if there is only ip6=...
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) |
|
| 2016-12-02 16:13:22 |
Scott Moser |
description |
http://pad.lv/1639930
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1639930
=== Begin SRU Template ===
[Impact]
On a system booted with both ip6= and ip= on the kernel command line
cloud-init will raise an exception and fail to process user-data and
have its normal affect on boot.
That is because cloud-init previously raised an exception when more
than one file in /run/net*.conf declared the same DEVICE. Changes to
isc-dhcp and initramfs-tools have changed their behavior and cloud-init
has to adjust to allow DEVICE6= and DEVICE= in separate files.
[Test Case]
Boot a system on a network with both ipv4 and ipv6 dhcp servers,
and pass kernel command line with:
ip=dhcp ip6=dhcp
[Regression Potential]
Regression seems unlikely as this is relaxing a check. Where previously
an exception would have been raised, cloud-init will now go on.
So it seems most likely, something that didn't work before (due to raised
exception) would now still not work, but with failures. That is not
expected, but that would likely be where regressions were found.
=== End SRU Template ===
In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='.
The code currently will return with no network configuration found if there is only ip6=...
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) |
=== Begin SRU Template ===
[Impact]
On a system booted with both ip6= and ip= on the kernel command line
cloud-init will raise an exception and fail to process user-data and
have its normal affect on boot.
That is because cloud-init previously raised an exception when more
than one file in /run/net*.conf declared the same DEVICE. Changes to
isc-dhcp and initramfs-tools have changed their behavior and cloud-init
has to adjust to allow DEVICE6= and DEVICE= in separate files.
[Test Case]
Boot a system on a network with both ipv4 and ipv6 dhcp servers,
and pass kernel command line with:
ip=dhcp ip6=dhcp
[Regression Potential]
Regression seems unlikely as this is relaxing a check. Where previously
an exception would have been raised, cloud-init will now go on.
So it seems most likely, something that didn't work before (due to raised
exception) would now still not work, but with failures. That is not
expected, but that would likely be where regressions were found.
=== End SRU Template ===
In changes made under bug 1621615 (specifically a1cdebdea), we now expect that there may be a 'ip6=' argument on the kernel command line. The changes made did not test the case where there is 'ip6=' and no 'ip='.
The code currently will return with no network configuration found if there is only ip6=...
Related bugs:
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
* bug 1621507: initramfs-tools configure_networking() fails to dhcp IPv6 addresses
* bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) |
|
| 2016-12-02 18:15:42 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
In Progress |
|
| 2016-12-09 18:20:35 |
Robie Basak |
cloud-init (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-12-09 18:20:37 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-12-09 18:20:42 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2016-12-09 18:20:45 |
Robie Basak |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2016-12-09 18:23:07 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2016-12-12 01:53:41 |
Scott Moser |
cloud-init: status |
Confirmed |
Fix Committed |
|
| 2016-12-16 15:52:25 |
Scott Moser |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2016-12-16 17:02:59 |
Scott Moser |
attachment added |
|
verification log on xenial https://bugs.launchpad.net/cloud-init/+bug/1639930/+attachment/4792426/+files/verify.txt |
|
| 2016-12-16 17:03:36 |
Scott Moser |
attachment added |
|
go: the tool in the log that patched the image and copied out kernel/initrd https://bugs.launchpad.net/cloud-init/+bug/1639930/+attachment/4792427/+files/go |
|
| 2016-12-19 16:27:40 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-12-19 16:27:56 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-12-23 17:35:57 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2017-01-04 18:44:06 |
LaMont Jones |
maas: status |
New |
Fix Released |
|
| 2017-01-12 19:47:17 |
Brian Murray |
cloud-init (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2017-01-12 19:47:20 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-01-12 19:47:28 |
Brian Murray |
tags |
maas-ipv6 verification-done |
maas-ipv6 |
|
| 2017-01-12 19:47:29 |
Brian Murray |
tags |
maas-ipv6 |
maas-ipv6 verification-needed |
|
| 2017-01-20 18:09:44 |
Scott Moser |
attachment added |
|
log showing verification on yakkety https://bugs.launchpad.net/cloud-init/+bug/1639930/+attachment/4806841/+files/yakkety-verify.log |
|
| 2017-01-20 18:09:59 |
Scott Moser |
tags |
maas-ipv6 verification-needed |
maas-ipv6 verification-done |
|
| 2017-01-30 18:18:12 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2023-05-10 18:05:46 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2756 |
|
