Comment 2 for bug 1819365

Juju defaults to 'least-used' HA placement. (So if you deploy APP -n3, we
will spread the units of the app to AZ1, AZ2, AZ3 to actually get the
benefit of *availability* zones to prevent a single failure from taking out
multiple units).
I believe we do have code that says "try the next AZ, if we get a failure
provisioning there, skip that AZ and try the next one". However, we need to
understand the failure is AZ specific, and not some other
could-never-be-satisfied error.

On Sun, Mar 10, 2019 at 10:45 PM Pedro Guimarães <email address hidden>
wrote:

> I've found a similar bug: https://bugs.launchpad.net/juju/+bug/1786309.
> But I consider it is discussing a different issue, with same final
> error.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1819365
>
> Title:
> Zone constraints causes placement to fail although there available
> machines
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1819365/+subscriptions
>