Comment 44 for bug 1902960

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,