Comment 6 for bug 1793564

The current Juju behaviour is to return this error if both of these conditions are true:
- There is more than one usable address on the machine.
- There is no configuration value for juju-ha-space.

By usable addresses we mean cloud-local, but we fall back to a public address if there are none of those.

Prior to 2.4, Juju would attempt to set the space transparently by interrogating the addresses, but this had some edge cases, so we decided to be explicit and require the user to specify a space to use whenever multiple addresses are detected.

If a space is configured for HA, then the first address returned from the space is used. So you can work around this just be setting juju-ha-space.