[Touch-packages] [Bug 1631474] Please test proposed package
Hello scotte, or anyone else affected, Accepted initramfs-tools into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.125ubuntu6.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Committed Status in initramfs-tools source package in Zesty: In Progress Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631474] Please test proposed package
Hello scotte, or anyone else affected,
Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in initramfs-tools source package in Xenial:
Fix Committed
Status in initramfs-tools source package in Yakkety:
Fix Committed
Status in initramfs-tools source package in z-series:
Fix Committed
Bug 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631474] Please test proposed package
Hello scotte, or anyone else affected,
Accepted initramfs-tools into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.125ubuntu6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in initramfs-tools source package in Xenial:
Fix Committed
Status in initramfs-tools source package in Yakkety:
Fix Committed
Status in initramfs-tools source package in z-series:
Fix Committed
Bug 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
