On Fri, Nov 17, 2017 at 11:33 AM, john <email address hidden> wrote:
> Yes we know the configurations are different. these are two different
> test environments. We updated one of our tests labs first and found the
> problems. at the time both were working under 505. I'm providing
> this only as a reference. The problems are not to do with these
> difference.
>
Correct; in both cases, if you want to interact with any of the interfaces
that are not marked 'auto'; then your commands need to append --allow
<class>
In particular, the error reported was an interface that was part of br-ext,
so
it would need ifup --allow br-ext eth1.10
On Fri, Nov 17, 2017 at 11:33 AM, john <email address hidden> wrote:
> Yes we know the configurations are different. these are two different
> test environments. We updated one of our tests labs first and found the
> problems. at the time both were working under 505. I'm providing
> this only as a reference. The problems are not to do with these
> difference.
>
Correct; in both cases, if you want to interact with any of the interfaces
that are not marked 'auto'; then your commands need to append --allow
<class>
In particular, the error reported was an interface that was part of br-ext,
so
it would need ifup --allow br-ext eth1.10
> /bugs.launchpad .net/bugs/ 1732202 interface /bugs.launchpad .net/curtin/ +bug/1732202/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Xenial Deploy fails when using /etc/network/
>
> To manage notifications about this bug go to:
> https:/
>