That would be a different bug, unfortunately. Mine was specifically down to ipconfig not handling multiple network interfaces correctly, triaged and successfully fixed by Canonical, and exhaustively validated in our infrastructure.
Roughly speaking, it would quickly loop through the interfaces sending out DHCP requests, and then listen on all for the responses, but it was only able to track the request for one interface, which was whatever the last interface it sent the request out of. There's a session id associated with it, and if that didn't match it would drop the packets. Booting became dependent on the order of network interfaces returned by the kernel, something that isn't guaranteed in any way, and explains why it was working with some kernels and not with others, as it would only work if the one interface that got DHCP responses was the last one returned by the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652348 Title: initrd dhcp fails / ignores valid response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1652348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
