Using bridges defined by MAAS 2.1 makes Juju and Mongo eat lots of CPU and RAM

[Andrew McDermott]

In MAAS 2.1 you can now define bridged interfaces.

If you bootstrap Juju against a machine configured with bridges juju repeatedly logs an error:

{github.com/juju/juju/state/machine_linklayerdevices.go:641: cannot set link-layer device addresses of machine "0"} {github.com/juju/juju/state/machine_linklayerdevices.go:641: }

The worker dies and restarts:

2016-11-24 21:34:51 TRACE juju.worker.dependency engine.go:608 restarting dependents of "machiner" manifold
2016-11-24 21:34:51 TRACE juju.worker.dependency engine.go:422 starting "machiner" manifold worker in 3.05s...

and the process repeats causing Juju and Mongo to use a lot of CPU, and for mongo lots of RAM (>1GB).

This is because the MAAS provider does not cater for the "bridge" type.

[Andrew McDermott (frobware)]

WIP - https://github.com/frobware/juju/tree/juju-and-monogo-eats-all-my-ram

[Andrew McDermott (frobware)]

PR - https://github.com/juju/juju/pull/6618

[Andrew McDermott (frobware)]

See also: https://bugs.launchpad.net/juju/+bug/1643897