Ryan Harper [2016-10-28 18:46 -0000]: > netplan generator only emits the "systemd-networkd" target wants, so > if we use After=systemd-networkd-wait-online; that's never run since > nothing wants it.
Right, if you want it, you need to pull it in yourself. > If we add it explicitly, then it runs even when networkd doesn't Oh, indeed -- it quickly ends with "Dependency failed" as networkd is just a Requisite=, not a Requires=. So this actually does give you exactly the semantics that we want, no? *If* networkd is running then it waits for it, otherwise it's a no-op. @Steve: ^ So I take back my previous comment -- it seems Requires/After=s-n-wait-online.service is actually exactly what we want after all. > I did play with it, but the networkd in xenial blocks for some non-trivial > amount of time (10s of seconds) > if dbus.service is not up. OK, that's something to look into then. It doesn't hang if there's no configuration (i. e not trivially reproducible), I'll check if I can reproduce this with a real config ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs