Comment 4 for bug 1817564

Hi, I am trying juju 2.6/candidate snap.
I manually added 3 machines to my controller model; run:

juju enable-ha -c controller --to=1,2

That complains on missing juju-ha-space configurations: ERROR juju-ha-space is not set and a unique usable address was not found for machines: 0

Also, during enable-ha, all machines on controller model went to "down" state; although their own systemctl jujud-machine-X was "active(running)".

juju show-machine -m controller 0/1/2 shows that all controllers have 2 networks and they can reach each on one of them.

Here is full crashdump: https://drive.google.com/open?id=15NMlsZ3ZT8oniE52HNLqN9zAcoh50P6O

Some notices: I've added a model and 30 machines to this model before enabling controller HA.
I've run a successful enable-ha on an AWS environment, using 3 machines (bigger, with 8 vcpus and 32G, rather than 4cpus / 8G).

Machines on model started to flip between "started" and "down" after I've ran this command.

This is an ongoing deployment for a customer.