Comment 33 for bug 1463480

Both private and public addresses are determined this way - from a merged list of what the provider tells us about the machine and what we can see on the machine itself, which is then sorted by value (e.g. 10.10.0.10 before 10.11.0.10) and scope (public, local-cloud, local-machine for public-address; local-cloud, local-machine, public for private-address). Provider addresses and instance status are polled frequently (every few seconds) until "running", then less frequently (every 15m). Machine addresses are read once on machine agent startup and updated (filtering lxcbr0 addresses first, if any). Changes to machine addresses are not detected unless the machine agent is restarted (or of course after a reboot). So the machine addresses shouldn't be a problem really.

Is it possible that setting the VIP address set by corosync/pacemaker somehow triggers either a restart of the machine agent or changes what juju sees in the 'ip_addresses' field of MAAS node details API?

I've seen somewhere in the logs that disable-network-management environment setting is set to true. Why is that? This means juju won't create juju-br0 on MAAS.

Let's sync up on IRC - when will you be available?