Juju doesn't attempt to evenly distribute controllers across AZs, when on OpenStack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Hello Juju team.
I'm running juju 2.8.9 with OpenStack as cloud provider having availability zones AZ1,AZ2,AZ3 created.
When running "juju enable-ha -n 3" one would expect Juju to attempt to distribute controller VMs one per OpenStack AZ if available. However that doesn't happen:
$ juju status -m controller
Model Controller Cloud/Region Version SLA Timestamp
controller o7k-ctrl openstack_
Machine State DNS Inst id Series AZ Message
0 started 10.254.10.103 0314afdc-
1 started 10.254.10.34 45299b55-
2 started 10.254.10.124 33800af7-
For the sake of completeness, in public clouds the behavior is the same and highlighted in the documentation:
https:/
The workaround for me is to "juju enable-ha --constraints zones=AZ2,AZ3" assuming that the first controller bootstraps to a VM on AZ1 by default.
Changed in juju: | |
milestone: | none → 2.9.1 |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: enable-ha openstack-provider |
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Changed in juju: | |
milestone: | 2.9.3 → 2.9-next |
Changed in juju: | |
milestone: | 2.9-next → 3.1-beta1 |
Changed in juju: | |
milestone: | 3.1-beta1 → 3.1-rc1 |
Changed in juju: | |
milestone: | 3.1-rc1 → 3.1-rc2 |
Changed in juju: | |
milestone: | 3.1-rc2 → 3.1-rc3 |
We're experiencing this bug as well.