My initial conclusion may not have been correct. I now think that the fix in iproute2 4.15.0-2ubuntu1.3 made the problem more apparent.
The Network Name Resolution service is not actually failing. It is being stopped and restarted (based on the logs). So the real problem seems to be a very aggressive approach to restarting the Network Name Resolution service. In our case, the DHCPClient request is not getting a response, yet the Network Name Resolution service is still being restarted. Mar 13 03:43:32 em-vf-ns1 dhclient[3443]: DHCPDISCOVER on nsblk01 to 255.255.255.255 port 67 interval 5 (xid=0xe499a07d) Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No DHCPOFFERS received. Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No working leases in persistent database - sleeping. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopping Network Name Resolution... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopped Network Name Resolution. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting Network Name Resolution... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started Network Name Resolution. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting resolvconf-pull-resolved.service... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started resolvconf-pull-resolved.service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919003 Title: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
