Comment 9 for bug 1732202

I just added /etc/network/interfaces.

/etc/network/interfaces/* was empty.

John Casey
CPlane Networks
Direct: 415-215-0854

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Ryan Harper
Sent: Tuesday, November 14, 2017 9:39 AM
To: John Casey <email address hidden>
Subject: Re: [Bug 1732202] Re: Xenial Deploy fails when using /etc/network/interface

Sorry,

If you can provide a copy of /etc/network/interfaces
/etc/network/interfaces.d/* files one of the deployed nodes where it is not broken.

Ryan

On Tue, Nov 14, 2017 at 11:26 AM, john <email address hidden> wrote:

> I don't know what an eni file is. can you please give more instruction.
> We are not using any late_commands. Everything is done using juju charms.
> please see our charms code.
>
> ** Changed in: curtin
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the
> bug report.
> https://bugs.launchpad.net/bugs/1732202
>
> Title:
> Xenial Deploy fails when using /etc/network/interface
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1732202/+subscriptions
>

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1732202

Title:
  Xenial Deploy fails when using /etc/network/interface

Status in curtin:
  New
Status in MAAS:
  Invalid

Bug description:
  MAAS 2.2.2 Move from Curtin 505 to 532 breaks use of
  /etc/network/interface.

  Our OVS OpenStack charm modifies /etc/network/interfaces to set up OVS and adds ethtool tso=off,tro=off, etc.
  We've deployed this charm in production at PCCW. PCCW updated their MAAS server and the charm no longer works.

  in curtin 532, /etc/network//interfaces is empty. The new
  definitions are in /etc/network/interfaces.d/50-cloud-init.cfg

  Attaching charm code and juju-log file

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1732202/+subscriptions