Running the test case from the bug description for a yakkety container, this is the behavior I see with the yakkety-updates version of nplan:
-- Logs begin at Thu 2017-04-20 05:38:36 UTC, end at Thu 2017-04-20 05:40:08 UTC. -- Apr 20 05:38:36.302406 y1 systemd[1]: Started Nameserver information manager. Apr 20 05:38:36.570955 y1 systemd[1]: resolvconf.service: Failed to reset devices.list: Operation not permitted Apr 20 05:38:37.434155 y1 systemd[1]: systemd-networkd-wait-online.service: Failed to reset devices.list: Operation not permitted Apr 20 05:38:37.434853 y1 systemd[1]: Starting Wait for Network to be Configured... Apr 20 05:38:37.443689 y1 systemd-networkd-wait-online[218]: ignoring: lo Apr 20 05:38:37.564242 y1 systemd[1]: systemd-networkd-wait-online.service: Failed to reset devices.list: Operation not permitted Apr 20 05:38:37.564969 y1 systemd[1]: resolvconf.service: Failed to reset devices.list: Operation not permitted Apr 20 05:38:50.119398 y1 systemd[1]: Started Wait for Network to be Configured. Apr 20 05:38:50.120176 y1 systemd[1]: Reached target Network is Online. Apr 20 05:38:50.132004 y1 systemd[1]: systemd-networkd-wait-online.service: Failed to reset devices.list: Operation not permitted That doesn't appear to match the expected "bad" behavior. Ryan, do you know what I'm missing here? I'm assuming it's a container permissions error, and give a VM a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649931 Title: systemd-networkd needs to ensure DNS is up before network- online.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
