Comment 10 for bug 1758919

Is this actually Field Critical? Isn't just moving the post-up to a
different section enough to fix the field issue as a workaround?

On Mon, Mar 26, 2018 at 6:26 PM, John Meinel <email address hidden> wrote:

> Note that:
> https://launchpadlibrarian.net/362140579/50-cloud-init.cfg
> Is a lie, because it pretends that it is just setting up the "post-up"
> routes "after all interfaces", but really all of those are explicitly
> attached to bond2 (it though it wasn't indenting them, but ifup, et al,
> don't actually pay attention in that fashion.)
>
>
> On Mon, Mar 26, 2018 at 6:24 PM, John Meinel <email address hidden>
> wrote:
>
>> Why is adding it to the "last interface" correct. Wouldn't it be more
>> correct to attach routes to the interface that contains that route?
>>
>> Eg, in your above scenario, bond0 is getting 100.99.4.3/24 thus things
>> that use the 100.99.4.254 as the gateway should be attached to bond0?
>>
>> On Mon, Mar 26, 2018 at 5:59 PM, Gábor Mészáros <
>> <email address hidden>> wrote:
>>
>>> ** Attachment added: "50-cloud-init.cfg"
>>> https://bugs.launchpad.net/juju/+bug/1758919/+attachment/50
>>> 91207/+files/50-cloud-init.cfg
>>>
>>> --
>>> You received this bug notification because you are a member of Canonical
>>> Field Critical, which is subscribed to the bug report.
>>> Matching subscriptions: juju bugs
>>> https://bugs.launchpad.net/bugs/1758919
>>>
>>> Title:
>>> static routes get lost when lxd container being deployed [MAAS
>>> environment]
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/juju/+bug/1758919/+subscriptions
>>>
>>
>>
>