Comment 6 for bug 1933690

I thought at start up we pulled through what AZs were in used from our list
of machines. If we aren't then the provisioning code is certainly incorrect.

On Wed, Jul 7, 2021 at 9:50 PM Ian Booth <email address hidden> wrote:

> In investigating this bug, I have found a related issue. To allocate
> machines across AZs, the provisioner worker maintains a list of the AZs
> and how many machines are in each one. But, this list is reset any time
> the controller agent restarts, so after an upgrade for example, all the
> known machine allocations are set back to 0 and Juju makes poor
> decisions from that point about how to allocate the machines. So this
> makes the issue as one that needs fixing.
>
> ** Changed in: juju
> Importance: Wishlist => High
>
> ** Changed in: juju
> Assignee: (unassigned) => Ian Booth (wallyworld)
>
> ** Changed in: juju
> Status: Triaged => In Progress
>
> ** Changed in: juju
> Milestone: 2.9-next => 2.9.9
>
> ** Summary changed:
>
> - openstack : juju doesn't distribute units across AZs
> + juju doesn't randomise AZ selection where AZs have equal machines
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1933690
>
> Title:
> juju doesn't randomise AZ selection where AZs have equal machines
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1933690/+subscriptions
>