Comment 26 for bug 1532167

@andrew - I finally got LXC containers working again using your patched Juju. The issue is not how the bonds are configured (802.3ad works fine). The problem is that when you are using VLAN tagging (like I am) you must attach the juju-br0 bridge to a VLAN interface (e.g. eth0.123 or bond0.456) so that both the LXC machine and the MAAS server (providing DHCP) are sending tagged traffic. Otherwise the LXC cannot pull DHCP, and the deploy fails.

I reset my environment to use only eth0 set to the default VLAN. Juju could bootstrap just fine, and created juju-br0 attached to eth0. However it still could not create any LXC containers. They would hang trying to get a DHCP address, and eventually give up.

However if I manually create a VLAN interface for the default VLAN and attach the juju-br0 bridge to it, LXC containers start up normally, both when using the bonded interface and plain eth0. So I rewrote the /e/n/i file to create a bond0.1, then attached the juju-br0 bridge to that. That started working.

Anyway, it's an interesting quirk of the networking regarding VLANs.