I've tested this now in a 16.10 VM, and I can't verify this SRU because
I can't confirm the buggy behavior.  Adjusting the journalctl command
for changed unit names in 16.10, I get:

# journalctl -o short-precise --unit resolvconf.service --unit 
network-online.target --unit systemd-networkd-wait-online.service --unit 
systemd-networkd.service --no-pager
-- Logs begin at Thu 2017-04-20 07:07:07 UTC, end at Thu 2017-04-20 07:08:09 
UTC. --
Apr 20 07:07:08.973024 ubuntu systemd[1]: Starting Network Service...
Apr 20 07:07:09.013394 ubuntu systemd-networkd[958]: Enumeration completed
Apr 20 07:07:09.013744 ubuntu systemd[1]: Started Network Service.
Apr 20 07:07:09.015259 ubuntu systemd[1]: Starting Wait for Network to be 
Apr 20 07:07:09.023517 ubuntu systemd-networkd[958]: ens3: IPv6 enabled for 
interface: Success
Apr 20 07:07:09.026605 ubuntu systemd-networkd[958]: ens3: Gained carrier
Apr 20 07:07:09.030066 ubuntu systemd-networkd[958]: ens3: DHCPv4 address via
Apr 20 07:07:09.030329 ubuntu systemd-networkd[958]: ens3: Not connected to 
system bus, ignoring transient hostname.
Apr 20 07:07:10.100496 ubuntu systemd-networkd[958]: ens3: Gained IPv6LL
Apr 20 07:07:22.841001 ubuntu systemd-networkd[958]: ens3: Configured
Apr 20 07:07:22.843432 ubuntu systemd-networkd-wait-online[971]: ignoring: lo
Apr 20 07:07:22.849021 ubuntu systemd[1]: Started Wait for Network to be 
Apr 20 07:07:22.850384 ubuntu systemd[1]: Reached target Network is Online.

Notably, I don't see any output here about resolvconf.

# systemctl status resolvconf.service --no-pager
‚óŹ resolvconf.service - Nameserver information manager
   Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2017-04-20 07:14:42 UTC; 4min 25s ago
     Docs: man:resolvconf(8)
 Main PID: 659 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/resolvconf.service

Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.

I don't know why the journal is being rotated.

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  systemd-networkd needs to ensure DNS is up before network-

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to