Hi, We are affected by this issue on Bionic. Upgrading systemd package breaks DNS resolution in VMs that didn't have the workaround above applied. Would it be possible to provide a backport of the systemd fix done to Bionic?
We are currently relying on the following workaround to recover from the loss of DNS resolution: udevadm trigger -c add /sys/class/net/eth0 systemctl restart systemd-networkd It seems that we are able to consistently reproduce this problem in our VM images, we had multiple VM images affected by this issue. We'd be happy to provide debug information if you want to investigate the root cause further. Of course I can't tell for sure if the next VM image we build will be affected or not. Thanks, -- 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
