juju.NewAPIConnection doesn't fall back to using UnresolvedAPIEndpoints when connecting

[Roger Peppe]

This may be by design but it surprised me, hence this bug report.

The controller information caches both APIEndpoints and UnresolvedAPIEndpoints.
The unresolved endpoints are useful to keep because their respective
IP addresses might change - they're the primary source.

However the API connection code never falls back to using UnresolvedAPIEndpoints - it
will always use the resolved IP addresses acquired after the most recent
API connection which might now be wrong.

When writing code to set manually create a controller entry, it would seem logical
to put the (unresolved) API addresses into UnresolvedAPIEndpoints,
but this won't work - instead one must put the unresolved API addresses
into APIEndpoints. This seems wrong.

As a solution, I'd suggest falling back to using the unresolved addresses after
trying all the resolved addresses.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.