It's been resolved for us in xenial for quite awhile...
--
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.122ubunt
Thanks Eric, we will remove our local workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
Title:
zfs services fail on firstboot if zfs-utils is integrated
Sorry for not linking the bug here initially, that's my fault and I
apologize...
--
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/1628306
Title:
network booting fail
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 acknowl
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 initramfs
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 i
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 cor
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
Touch seeded packages
Public bug reported:
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
dif
initramfs-tools 0.122ubuntu8.3 has resulted in a serious regression for
instances running in AWS when the ip=dhcp boot option set.
0.122ubuntu8.2 (and previous versions) do not exhibit the problem.
I'll create a new issue for tracking, but wanted to add a comment here.
--
You received this bug n
I tested again with xenial-proposed and confirmed that everything looks
good as far as systemd no longer failing ZFS units due to no /etc/mtab.
ii libzfs2linux 0.6.5.6-0ubuntu14 amd64
Native OpenZFS filesystem library for Linux
ii zfs-dkms
I tested this using my reproduction method in AWS EC2 with a test
package/PPA provided by Eric@Ubuntu (slashd) containing the commit
referenced in comment #6.
All looks good now - systemd units for ZFS no longer fail. Thanks for
moving this along!
--
You received this bug notification because yo
12 matches
Mail list logo
