On Tue, Dec 13, 2016 at 10:02 AM, Martin Pitt <email address hidden>
wrote:
> Ryan Harper [2016-12-06 12:54 -0000]:
> > The following change should go against systemd-networkd-wait-
> > online.service
> >
> > + # Ensure that DNS is working before reaching online target
> > + After=systemd-networkd-resolvconf-update.service
>
> For the record, this should be the other way around -- add
> Before=systemd-networkd-wait-online.service to
> s-n-resolvconf-update.service. The latter is a Debian downstream unit
> and thus avoids carrying a patch to an upstream unit that refers to a
> downstream one.
>
Well, ideally we'd have both. Part of the challenge in dealing with
systemd units is that it's very difficult to determine the ordering.
If one doesn't look at the right file.
I won't push for a delta but I do think that these unit relationships ought
to be explicit on both sides.
On Tue, Dec 13, 2016 at 10:02 AM, Martin Pitt <email address hidden>
wrote:
> Ryan Harper [2016-12-06 12:54 -0000]: networkd- wait- networkd- resolvconf- update. service systemd- networkd- wait-online. service to update. service. The latter is a Debian downstream unit
> > The following change should go against systemd-
> > online.service
> >
> > + # Ensure that DNS is working before reaching online target
> > + After=systemd-
>
> For the record, this should be the other way around -- add
> Before=
> s-n-resolvconf-
> and thus avoids carrying a patch to an upstream unit that refers to a
> downstream one.
>
Well, ideally we'd have both. Part of the challenge in dealing with
systemd units is that it's very difficult to determine the ordering.
If one doesn't look at the right file.
I won't push for a delta but I do think that these unit relationships ought
to be explicit on both sides.
> /bugs.launchpad .net/bugs/ 1636912 /bugs.launchpad .net/systemd/ +bug/1636912/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> systemd-networkd runs too late for cloud-init.service (net)
>
> To manage notifications about this bug go to:
> https:/
>