systemd-resolve is missing nameservers until interface is bounced

Bug #1802355 reported by Jason Hobbs on 2018-11-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)

Bug Description

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

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:

Jason Hobbs (jason-hobbs) wrote :

I've configured our test runs to turn debug logging on for networkd and resolvd.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers