On Tue, Dec 13, 2016 at 10:02 AM, Martin Pitt
wrote:
> Ryan Harper [2016-12-06 12:54 -]:
> > 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.ser
Ryan Harper [2016-12-06 12:54 -]:
> 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
B
Steve Langasek [2016-10-29 4:38 -]:
> cloud-init does not *require* you to be online. It *requires* you to
> provide a data source
Yes, I know, that's exactly my point -- by design it should/does not
require you to be online, but by making it wait for
s-n-wait-online.target or network-online
Ryan Harper [2016-10-28 18:46 -]:
> 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 e
On Fri, Oct 28, 2016 at 06:46:07PM -, Ryan Harper wrote:
> > > we really want something like
> > > After=networking|networkd-wait-online
> > > which handles determining if networkd was supposed to run or not
> > That already exists, it's network-online.target -- whatever "implements"
> > it (
On Fri, Oct 28, 2016 at 06:02:29PM -, Martin Pitt wrote:
> > However, if there isn't a local seed, then we must search again *once*
> networking is up.
> But this "if there isn't a local seed" isn't something you can express as
> a static condition, hence my thought that it might be better if
On Fri, Oct 28, 2016 at 1:02 PM, Martin Pitt
wrote:
> > However, if there isn't a local seed, then we must search again *once*
> networking is up.
>
> Fair enough, but you can then of course not use that unit to configure
> the network.
Of course we can. We need to cycle the network though.
On Thu, Oct 27, 2016 at 3:57 PM, Martin Pitt
wrote:
> > cloud-init expects networking to be up, like 'networking.service'
> before it runs..
>
>
> It seems to me that this might have to be split into two parts then -- one
> that can provide network config which runs early and does not require
> n
On Thu, Oct 27, 2016 at 3:57 PM, Martin Pitt
wrote:
> > cloud-init expects networking to be up, like 'networking.service'
> before it runs..
>
>
> I think it needs to make up its mind -- why does it want to run
> Before=network-online.target then? I thought the idea was that cloud-init
> is able
On Thu, Oct 27, 2016 at 2:50 PM, Martin Pitt
wrote:
> > oddly though when using the ifupdown 'networking.service'; we don't
> need to use that target.
>
> Yes, that's a Type=oneshot, as it just calls "ifup -a". So that's more
> or less equivalent to s-n-wait-online --timeout=30 or After=s-n-wait-
On Thu, Oct 27, 2016 at 01:43:05PM -, Ryan Harper wrote:
> without resolved in 16.04 though the change isn't strictly needed but to
> keep the backported branch closer to trunk, I would expect those to come
> in.
Except it's not correct that we don't have resolved in 16.04. We're not
using r
On Thu, Oct 27, 2016 at 8:43 AM, Ryan Harper
wrote:
>
>
> On Thu, Oct 27, 2016 at 5:59 AM, Martin Pitt
> wrote:
>
>> So did I understand this right:
>>
>> * In current xenial, cloud-init runs in late boot, so there is no
>> principal ordering problem between cloud-init and networkd, other than
On Thu, Oct 27, 2016 at 5:59 AM, Martin Pitt
wrote:
> So did I understand this right:
>
> * In current xenial, cloud-init runs in late boot, so there is no
> principal ordering problem between cloud-init and networkd, other than
> that cloud-init.service should declare After=systemd-networkd.ser
On Wed, Oct 26, 2016 at 6:41 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> Note that the systemd dependencies shown for cloud-init in xenial (on
> which Ubuntu Core 16 is based) don't match those listed in the bug
> description. Instead, xenial currently has:
>
> After=cloud-init-lo
14 matches
Mail list logo
