Comment 17 for bug 1463480

Peter, I chatted with some folks about this again this afternoon, and there's not really anything we can do from a code change perspective since the upgrade failure is caused by a problem fixed in 1.22, and we are not releasing any more updates to 1.20. The one container, machine-0-lxc-0, just failed to update as the watcher lost its connection with the state server before getting the correct state server addresses.

If you hit this again, you should be able to manually modify the agent.conf file to remove the 10.0.3.1 address. I suspect they didn't show up as you mentioned in comment #12 because machine-0 at that time had been updated to 1.22, which filters them appropriately.

Regarding the HA VIP address, juju status picks one of the addresses associated with the machine to display as the public address, and I can see in the logs that machine-0-lxc-0 had both 172.20.171.204 and 172.20.168.104 assigned to it. Should it not have both?

I'll be around in the morning my time tomorrow if you want to chat on IRC about this.