smoser - I think you make a really good point. A regression in an LTS
distribution that results in a working configuration to no longer work
is fairly serious - as is introducing behavioral changes in an LTS.
While I'm generally in favor of fix-forward, it's not always the right
approach. I acknowledge changes are hard, and there's not always a clear
or right answer, especially given the vast diversity in exactly what
people do with their systems and how they configure them. This is a
larger discussion around change management, and my opinions here are a
bit off-topic as it relates specifically to this bug, so...
I retested with xenial-proposed and the system rebooted fine for me.
initramfs-tools:
Installed: 0.122ubuntu8.4
Candidate: 0.122ubuntu8.4
Version table:
*** 0.122ubuntu8.4 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
ii initramfs-tools 0.122ubuntu8.4 all
generic modular initramfs generator (automation)
ii initramfs-tools-bin 0.122ubuntu8.4 amd64
binaries used by initramfs-tools
ii initramfs-tools-core 0.122ubuntu8.4 all
generic modular initramfs generator (core tools)
--
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
