This has now migrated, please retest.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703640
Title:
nplan and
about nplan/libnss-resolve dependency. This issue has been resolved in
systemd, it appears that resolved has not been started from systemd
package at all, when it should have been since yakkety.
systemd (234-1ubuntu2) artful; urgency=medium
* Set UseDomains to true, by default, on Ubuntu.
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
** Changed in: dbus (Ubuntu)
Importance: Undecided => Critical
** Changed in: dbus (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
Network file was still the override I had from when RA was causing
problems. Same results after removal and re-applying netplan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1703640
Title:
nplan
Release: Artful/17.10
Manually removed libnss-resolve to simulate the result of only having
installed ubuntu-minimal (netplan configured with networkd as renderer).
1) Actual result is that /etc/resolv.conf is empty (except for
comments).
2) systemctl status systemd-resolved
*
Which release is this for?
The expected behaviour is for:
1) /etc/resolv.conf to point at resolved stub resolver 127.0.0.53
2) systemd-resolved.service enabled by default and started on boot
3) systemd-resolve --status connecting over dbus and displaying resolved status
4) libnss-resolve module
That would be the sane thing, however... Practically, without libnss-
resolve installed "systemd-resolve --status" returns an error about some
DBUS element and whether it is because of that or something else not
properly checked, you end up with nothing in /etc/resolv.conf and thus
without any DNS
I don't think it is; you should be able to use things just as well with
/etc/resolv.conf, and having systemd-networkd (or systemd-resolved)
update it, depending on whether this is automatic via DHCP or for a
static IP.
Regardless, in general I tend to agree libnss-resolve probably should be
