Comment 6 for bug 1590689

It's not clear that the generated ENI is the root cause of LACP failure. But for consistency we should move the address off the device that gets bridged.

> On 16 Jun 2016, at 08:03, Ante Karamatić <email address hidden> wrote:
>
> We also had a case where juju generated ENI and configured an IP on both
> bond and juju-br0. That breaks LACP.
>
> http://paste.ubuntu.com/17392160/
>
> I'm not sure if suggested code fixes this case too.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1590689
>
> Title:
> MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-
> br0 interfaces have the same IP address at the same time
>
> Status in juju-core:
> Fix Committed
> Status in juju-core 1.25 series:
> In Progress
> Status in MAAS:
> Invalid
>
> Bug description:
> Running MAAS 1.9.3 - Juju 1.25.5 - Ubuntu 14.04.04
>
> After a Juju bootstrap the Juju controller node remains with both the
> eth0 and the juju-br0 interfaces set at the same time and with the
> same IP.
>
> eth0 is defined in ENI as manual but also in interfaces.d/eth0.cfg as
> DHCP
>
> juju-br0 is defined in ENI as static and with the same eth0 IP
>
> It seems Juju rewrites /etc/network/interfaces, but doesn't
> remove/change /etc/network/interfaces.d/eth0.cfg. This results in one
> interface defined twice.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1590689/+subscriptions