| 2016-10-07 18:25:20 |
Scott Emmons |
bug |
|
|
added bug |
| 2016-10-07 18:44:28 |
Dave Chiluk |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-10-07 18:48:52 |
Dave Chiluk |
tags |
|
regression-update |
|
| 2016-10-07 18:49:09 |
Dave Chiluk |
bug |
|
|
added subscriber Mathieu Trudel-Lapierre |
| 2016-10-07 19:00:59 |
Dave Chiluk |
tags |
regression-update |
cpc regression-update sts |
|
| 2016-10-07 19:13:54 |
Dave Chiluk |
initramfs-tools (Ubuntu): assignee |
|
Dave Chiluk (chiluk) |
|
| 2016-10-07 19:14:10 |
Dave Chiluk |
initramfs-tools (Ubuntu): status |
New |
In Progress |
|
| 2016-10-07 21:12:03 |
Mathieu Trudel-Lapierre |
bug task added |
|
initramfs-tools (Ubuntu Xenial) |
|
| 2016-10-07 21:21:51 |
Jason Gerard DeRose |
bug |
|
|
added subscriber Jason Gerard DeRose |
| 2016-10-07 22:47:22 |
Dave Chiluk |
attachment added |
|
lp1631474.xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff |
|
| 2016-10-08 00:38:57 |
Ubuntu Foundations Team Bug Bot |
tags |
cpc regression-update sts |
cpc patch regression-update sts |
|
| 2016-10-08 00:39:05 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2016-10-08 01:52:09 |
Dave Chiluk |
attachment removed |
lp1631474.xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff |
|
|
| 2016-10-08 01:52:26 |
Dave Chiluk |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-10-08 02:03:53 |
Dave Chiluk |
attachment added |
|
lp1631474.xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff |
|
| 2016-10-08 02:13:36 |
Dave Chiluk |
attachment added |
|
lp1631474.yakkety.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff |
|
| 2016-10-08 02:41:28 |
Dave Chiluk |
description |
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not conifgured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
|
| 2016-10-08 02:42:30 |
Dave Chiluk |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-10-10 14:18:17 |
Launchpad Janitor |
initramfs-tools (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-10-11 19:26:43 |
Mathew Hodson |
initramfs-tools (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-10-11 19:26:46 |
Mathew Hodson |
initramfs-tools (Ubuntu): importance |
Undecided |
High |
|
| 2016-10-11 20:56:10 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2016-10-12 01:32:49 |
Dave Chiluk |
attachment removed |
lp1631474.yakkety.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff |
|
|
| 2016-10-12 01:33:00 |
Dave Chiluk |
attachment removed |
lp1631474.xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff |
|
|
| 2016-10-12 16:17:21 |
Dave Chiluk |
attachment added |
|
lp1631474.xenial.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff |
|
| 2016-10-12 16:23:27 |
Dave Chiluk |
attachment added |
|
lp1631474.yakkety.debdiff https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff |
|
| 2016-10-12 16:48:41 |
Dave Chiluk |
description |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not conifgured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
|
| 2016-10-12 16:51:31 |
Adam Conrad |
bug task added |
|
initramfs-tools (Ubuntu Yakkety) |
|
| 2016-10-12 17:35:31 |
Dave Chiluk |
description |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken
-
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
|
| 2016-10-12 18:10:49 |
Jason Gerard DeRose |
attachment added |
|
log.tgz https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4760012/+files/log.tgz |
|
| 2016-10-13 06:11:11 |
Martin Pitt |
nominated for series |
|
Ubuntu Z-series |
|
| 2016-10-13 06:11:11 |
Martin Pitt |
bug task added |
|
initramfs-tools (Ubuntu Z-series) |
|
| 2016-10-13 06:12:51 |
Martin Pitt |
initramfs-tools (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2016-10-13 06:12:56 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-10-13 06:13:01 |
Martin Pitt |
tags |
cpc patch regression-update sts |
cpc patch regression-update sts verification-needed |
|
| 2016-10-13 06:14:03 |
Martin Pitt |
initramfs-tools (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-10-13 06:14:07 |
Martin Pitt |
initramfs-tools (Ubuntu Z-series): status |
New |
Fix Committed |
|
| 2016-10-13 06:14:27 |
Martin Pitt |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2016-10-13 14:08:23 |
Scott Moser |
description |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken
-
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken
-
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
This bug is a regression of changes made under bug 1628306.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
|
| 2016-10-13 16:36:23 |
LaMont Jones |
bug |
|
|
added subscriber LaMont Jones |
| 2016-10-14 09:09:12 |
Juha Aatrokoski |
bug |
|
|
added subscriber Juha Aatrokoski |
| 2016-10-14 19:09:39 |
LaMont Jones |
tags |
cpc patch regression-update sts verification-needed |
cpc patch regression-update sts verification-done |
|
| 2016-10-14 20:07:45 |
Mathew Hodson |
initramfs-tools (Ubuntu Z-series): importance |
Undecided |
High |
|
| 2016-10-17 17:55:14 |
Launchpad Janitor |
initramfs-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-17 17:55:20 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-10-18 10:45:34 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2016-10-20 19:39:33 |
Launchpad Janitor |
initramfs-tools (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2016-10-20 19:59:39 |
Mathieu Trudel-Lapierre |
description |
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed ip=dhcp or ip=:::::eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
* Regressions potential is limited to machines using ip={""|::::*|on|any|dhcp} on the kernel command line. As this is already broken regression potential is minimal. This is common on machines that use nfsroot or otherwise pxe boot.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken
-
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
This bug is a regression of changes made under bug 1628306.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
[Impact]
* initramfs-tools SRUs introduced regressions in ip= syntax, which cause unexpected behavior
[Test Case]
* Create a machine that boots using an nfsroot.
* Use ip=:::::eth0:dhcp on the kernel command line. To set up
networking.
* Discover that the device never comes up because, networking is not configured correctly.
[Regression Potential]
Should be back to original behavior before ipv6 support was introduced in the past 2 or 3 SRUs.
[Other Info]
* There are a number of other issues in this code base that are not solved by this fix.
- The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken
-
* The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed.
This bug is a regression of changes made under bug 1628306.
====================Original Bug Description Follows==================
initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments.
Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured.
The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set.
AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. |
|
| 2016-10-20 19:59:44 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Xenial): status |
Fix Released |
In Progress |
|
| 2016-10-20 19:59:49 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Yakkety): status |
Fix Released |
In Progress |
|
| 2016-10-20 20:02:28 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Xenial): status |
In Progress |
Fix Released |
|
| 2016-10-20 20:02:46 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Zesty): status |
Fix Committed |
In Progress |
|
| 2016-10-20 20:07:40 |
Martin Pitt |
initramfs-tools (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2016-10-20 20:07:43 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-10-20 20:07:53 |
Martin Pitt |
tags |
cpc patch regression-update sts verification-done |
cpc patch regression-update sts |
|
| 2016-10-20 20:07:54 |
Martin Pitt |
tags |
cpc patch regression-update sts |
cpc patch regression-update sts verification-needed |
|
| 2016-11-11 18:21:56 |
Mathieu Trudel-Lapierre |
tags |
cpc patch regression-update sts verification-needed |
cpc patch regression-update sts verification-done |
|
| 2016-11-14 23:02:47 |
System76 |
bug |
|
|
added subscriber System76 |
| 2016-11-23 10:08:59 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2016-11-29 23:26:55 |
Chris Halse Rogers |
tags |
cpc patch regression-update sts verification-done |
cpc patch regression-update sts |
|
| 2016-11-29 23:26:56 |
Chris Halse Rogers |
tags |
cpc patch regression-update sts |
cpc patch regression-update sts verification-needed |
|
| 2016-12-19 14:30:42 |
LaMont Jones |
tags |
cpc patch regression-update sts verification-needed |
cpc patch regression-update sts verification-done |
|
| 2017-01-19 14:25:09 |
Launchpad Janitor |
initramfs-tools (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-05-02 13:09:39 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-05-02 13:09:42 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu): assignee |
Dave Chiluk (chiluk) |
|
|
| 2017-05-02 13:09:44 |
Mathieu Trudel-Lapierre |
initramfs-tools (Ubuntu Zesty): status |
In Progress |
Fix Released |
|
