Comment 20 for bug 1463480

Yes, the HA VIP would be assigned to one of the cluster nodes at all times -- but IMO it shouldn't show up as the juju "public-address" of a container, because it just isn't. Eg. one of the upshots of the VIP leakage is that the HA VIP shows up as the node address in corosync.conf, which corosync fails horribly on, as a VIP can't be a node address at the same time.

Regarding the lxcbr0 address, this is probably #1416928. When watching /var/lib/juju/agents/*/agent.conf one can see it gets set to some 10.0.3.0/24 for a short time, before getting reset to the correct metal addresses; likely the failing containers start in that time frame.