I actually ran that test incorrectly and I was still using 1.24.6 agents.
So, I re-deployed using 1.24.6 agents and then upgraded the deployment to 1.24.7.
So, all agents were running 1.24.7 and containers on physical hosts only had 1 NIC with one address on the management network.
I then modified the lxc configuration file for each container to add 2 additional NICs bridged to physical interfaces.
I restarted each of the containers and they obtained new addresses.
However, juju definitely switched the address on about 7 containers.
So, it would seem that even when I run the test after deployment plugging in new networks, the address can switch.
I actually ran that test incorrectly and I was still using 1.24.6 agents.
So, I re-deployed using 1.24.6 agents and then upgraded the deployment to 1.24.7.
So, all agents were running 1.24.7 and containers on physical hosts only had 1 NIC with one address on the management network.
I then modified the lxc configuration file for each container to add 2 additional NICs bridged to physical interfaces.
I restarted each of the containers and they obtained new addresses.
However, juju definitely switched the address on about 7 containers.
So, it would seem that even when I run the test after deployment plugging in new networks, the address can switch.
Final deployment status is here: pastebin. ubuntu. com/12896894/
http://