Public bug reported: On some deployments of bionic, using maas and juju, my system ends up not being able to resolve hostnames. This happens inconsistently, it seems like a race.
systemd-resolve is showing no nameservers https://pastebin.canonical.com/p/tyFw8TfSxk rharper had a look at one reproducing: 17:47 < rharper> jhobbs: ok, I'm not sure how it got into that state; but networkd showed all of the DNS servers as configured in it's setting (networkctl status) but resolved had none. I restarted resolvd, that did not help; then I downed one of the interfaces (ip link set down eth1.2734; ip link set eth1.2734 up) and networkd I guess poked resolved with the list of DNS servers and I can see /run/systemd/resovle/* and they are now 17:47 < rharper> populated with the configs here is the netplan: https://pastebin.ubuntu.com/p/8nGXgNmw9q/ ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: cdo-qa foundations-engine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802355 Title: systemd-resolve is missing nameservers until interface is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
