Comment 9 for bug 1397376

latest versions of deployer (0.4.x) try all addresses stored in the jenv
file in turn with short time outs, obviously one of them has to work else
the cli is broken. i agree though that juju enforcing go try all at once in
parallel is kinda of painful for any other language and juju should promote
index 0 for state server be 'public' ip address for the server. also as
noted on previous bugs about api-endpoints.. multiple state servers be
broken out instead of a flat list is useful to clients that actually want
to use multiple state servers.. rather than parallel connect to grab bag of
addresses of which only a few would ever work.

On Tue, Dec 2, 2014 at 11:24 AM, David Britton <email address hidden>
wrote:

> juju-deployer breaks with this change, which is how I discovered the
> problem (it's how our official instructions say to deploy the openstack
> autopilot).
>
> The 'openstack-installer' command from the 'openstack' ubuntu package
> calls juju-deployer directly, AIUI.
>
> ** Changed in: juju-core
> Status: Incomplete => New
>
> ** Changed in: juju-core/1.21
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1397376
>
> Title:
> maas provider: 1.21b3 removes ip from api-endpoints
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1397376/+subscriptions
>