On Thu, May 18, 2017 at 10:07:21AM -, wendal wrote:
> are there any update for ubuntu 14.04 ?
This bug is a regression of changes made under bug 1628306. Bug 1628306
never updated 14.04, so this bug doesn't affect (and never affected)
14.04. If you have a problem with the behaviour of ip=dhcp
are there any update for ubuntu 14.04 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option
To manage
AFAIK everything landed for this already in zesty (and thus in artful as
well). Not sure why it is still "In Progress".
I'm setting this to Fix Released; if there are any other issues anyway,
they should get their own bug so we can better track any possible SRUs.
** Changed in: initramfs-tools
This bug was fixed in the package initramfs-tools - 0.125ubuntu6.3
---
initramfs-tools (0.125ubuntu6.3) yakkety; urgency=medium
* Do not rely on debug variables from dhclient.
initramfs-tools (0.125ubuntu6.2) yakkety; urgency=medium
[ Mathieu Trudel-Lapierre ]
*
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
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.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
This is confusing. Yakkety has never (to date) had an SRU land. So the
proposed revert to Yakkety isn't actually a revert from Yakkety's
perspective. Doing so would mean a behavioural change to Yakkety users,
no?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For the record, releasing this is blocked by getting the fix into zesty.
Devel series first!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools
Verification completed on yakkety as well; the revert is working as
expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mathieu,
I tested your PPA package with Xenial: with no config changes on my end,
it's working as expected from my use case.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
It's been resolved for us in xenial for quite awhile...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option
To
scotte, Jason, could either of you verify that the revert returned
initramfs-tools in a state that works for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with
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.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Description changed:
[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.
+ * initramfs-tools SRUs introduced regressions in ip= syntax, which
This bug was fixed in the package initramfs-tools - 0.125ubuntu6
---
initramfs-tools (0.125ubuntu6) yakkety; urgency=medium
* Fix case where ip=dhcp and ip=:eth0 and other ip= instances exists on
the kernel command line (LP: #1631474)
* Also fixed an error discovered by
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.5
---
initramfs-tools (0.122ubuntu8.5) xenial; urgency=medium
* scripts/functions: Revert configure_networking changes to the state at
0.122ubuntu8.1. (LP: #1631474)
-- Mathieu Trudel-Lapierre
** Changed in: initramfs-tools (Ubuntu Z-series)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and
After more discussion, marking this verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No
I have confirmed that this functions as expected for MAAS (behaves
exactly like 0.122ubuntu8.1 did.) Not marking verification-done, but +1
from me/MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue
for my use-case.
But I'm not changing verification-needed to verification-done yet as I
don't know if it fixes the use case of the original reporter.
@scotte - can you please confirm whether this fixes things for you?
--
Seems to me like we're at the point where considering a straight revert
of the SRU would be in order (and I'm certainly considering it for the
short term), in order to move forward again at a later time when this is
more solid -- not that the end goal is still going to be happening
(though maybe
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
0.122ubuntu8.4 still fails to get an IP when the switchport is not
'portfast' (and the switch therefore passes no traffic for 60 seconds
after link-up.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, and to be clear, I have no problem with this change in Yakkety. It's
just starting to feel a bit too invasive in my opinion for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
@martin - I tested the proposed package, and it's workable, but there
are behavior changes still compared to prior to when this regression was
introduced (in particular, the boot is a lot slower when there are
mulitple NICs but only one will be configured, even when I use
"ip=:eth0:dhcp").
Hi,
I think the right way to fix this regression would have been to revert the
change.
The change made in bug 1628306 made fairly wide spread changes. It caused this
regression as seen, but also added behavioral changes.
Previously, 'ip=dhcp' would do a ipv4 dhcp request (via ipconfig).
The
Note: I accepted this into -proposed as 'ip: ether "dev" is duplicate,
or "permanent" is garbage' seems to be an unrelated bug. Of course feel
free to fix that one as well with a subsequent upload, but this still
appears to be an incremental fix as-is.
** Changed in: initramfs-tools (Ubuntu
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.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Attaching a tarbal of everything i have in /var/log, not sure it's
useful (not my "ephemeral" environment is read-only with /var/log on a
tmpfs, so it's mostly empty).
Also here's my exact /proc/cmdline from within the booted ephemeral
environment:
BOOT_IMAGE=vmlinuz-4.4.0-42-generic
@chiluk - I tested the latest package in your PPA, but something seems
slightly wonky for my use case.
Networking seems to come up correctly, but it takes longer than it
should and I see warnings like this repeated several times:
ip: ether "dev" is duplicate, or "permanent" is garbage
--
You
** Description changed:
[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.
The latest PPA (0.122ubuntu8.3+lp1631474b2) passes verification for me.
$ cat /proc/cmdline
root=LABEL=cloudimg-rootfs ro console=hvc0 ip=dhcp tsc=reliable
$ dpkg -l|grep initramfs-tools
ii initramfs-tools 0.122ubuntu8.3+lp1631474b2 all
generic modular
I tested maas's command line as well.
/proc/cmdline from a maas pxe boot is
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=192.168.1.5 iscsi_target_port=3260
** Also affects: initramfs-tools (Ubuntu Yakkety)
Importance: High
Assignee: Dave Chiluk (chiluk)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No
** Description changed:
[Impact]
- * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+ * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp
- * Regression-updates
+ * Regression-updates
- * The fix better parses the ip=
I have uploaded a new version of initramfs-tools to my ppa, I would
again appreciate testing on this. Notably I fixed an bug that was
causing all_netbootable_devices to be tried instead of the interface
specified on the command line.
I also now handle the case where ip=:bootif , which really
** Patch added: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Updated debdiff to handle ip=:bootif use case.
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
I also have had four computers in the last 2 days show this bug.
I reinstalled the OS in those cases, if I find the bug again, I'll test
the PPA.
Thanks for finding a fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My computers were not in AWS, they were desktops that I had physical
access to running ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools
** Patch removed: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff
** Patch removed: "lp1631474.xenial.debdiff"
** Changed in: initramfs-tools (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@chiluk - the package in your PPA fixes it from my use case, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [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.
** Patch added: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I fixed up the comment, and the changelog comment and resubmit the
debdiff.
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you
** Patch removed: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The attachment "lp1631474.xenial.debdiff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
I tested with the PPA and it looks good in an initial test. Before,
upgrading initramfs-tools and rebooting would result in AWS instance
being unreachable. Now, it looks good!
$ cat /proc/cmdline
root=LABEL=cloudimg-rootfs ro console=hvc0 ip=dhcp tsc=reliable
$ dpkg -l|grep initramfs-tools
ii
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I created a PPA with a proposed solution to this issue. If I could get
some testing with this ppa I would appreciate it. Additionally if you
test the ppa please report back and include your /proc/cmdline in your
comment.
Thank you,
Dave Chiluk
--
You received this bug notification because you
Woops I forgot to include the PPA
https://launchpad.net/~chiluk/+archive/ubuntu/lp1631474
I will remove this ppa when the package hits -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
As asked by chiluk on IRC, here's my PXE boot configuration (well,
representative one anyway, the exact kernel version will obviously
change):
DEFAULT ubuntu
LABEL ubuntu
LINUX vmlinuz-4.4.0-36-generic
APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dediff from 8.2 to 8.3.
http://launchpadlibrarian.net/286956415/initramfs-tools_0.122ubuntu8.2_0.122ubuntu8.3.diff.gz
** Tags added: cpc sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
option
To manage notifications
Here's the initial portion of console output, with only a couple of
minor redactions related to keys, hostname, MAC address.
The most important bit is:
ip: SIOCGIFFLAGS: No such device
Error getting hardware address for "dhcp": No such device
Where the "ip=dhcp" kernel is not being processed
This was on xenial, unknown if other versions are affected.
Related:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
60 matches
Mail list logo