Comment 4 for bug 1532167

I am moving this comment from a different bug (https://bugs.launchpad.net/juju-core/+bug/1516891) because it seems to have a slightly different signature when using bonded interfaces w/ VLANs. It appears that juju will create a bridge interface for every entry in /e/n/i that contains "bond0", but every bridge is named "juju-br0" (This is using MAAS 1.9 + Juju 1.25.2). This makes all the networks off of bond0 stop working, which causes the Juju charm deployment to fail. The same thing happens when attempting a "juju bootstrap"

Fortunately Juju seems to leave bond1 alone, so I can still SSH into the node through one of those interfaces and see what kind of mess it made.

I've attached my /e/n/i file with how it appears after Juju messes with it.