As I mentioned in the upstream systemd bug, it's still not clear what exactly is causing this, and the inability to reproduce it after the image first boot, or with another image with debug added, or with the latest image, means it will be impossible to verify any fix to this problem.
However, my best guess is udevd is somehow missing the 'add' uevent for the network device, as I described in the upstream bug. While I don't know why it would miss the event, the upstream commit e0e789c1e97e2cdf1cafe0c6b7d7e43fa054f151 should fix the problem, as it will setup the proper udevd device parameters not only for 'add' but also 'change' uevents. So, based on those assumptions/guesses and on the relative safety of the upstream commit, I plan to SRU that commit for this bug. ** Bug watch added: github.com/systemd/systemd/issues #17532 https://github.com/systemd/systemd/issues/17532 ** Also affects: systemd via https://github.com/systemd/systemd/issues/17532 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902960/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
