failed to deploy bundle with "suitable availability zone for machine <num> not found"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Harry Pidcock |
Bug Description
It looks like when the order of machines list is not in order for zones, it fails to deploy the machines with an error message "suitable availability zone for machine <num> not found".
It is easily reproducible on aws.
The following bundle will fail on machine '2'.
series: bionic
machines:
"0":
constraints: zones=ap-
"1":
constraints: zones=ap-
"2":
constraints: zones=ap-
applications:
ubuntu1-1a:
charm: cs:ubuntu
num_units: 1
to:
- '0'
ubuntu2-1d:
charm: cs:ubuntu
num_units: 1
to:
- '1'
ubuntu3-1a:
charm: cs:ubuntu
num_units: 1
to:
- '2'
However, this bundle will succeed.
series: bionic
machines:
"0":
constraints: zones=ap-
"1":
constraints: zones=ap-
"2":
constraints: zones=ap-
applications:
ubuntu1-1a:
charm: cs:ubuntu
num_units: 1
to:
- '0'
ubuntu2-1d:
charm: cs:ubuntu
num_units: 1
to:
- '2'
ubuntu3-1a:
charm: cs:ubuntu
num_units: 1
to:
- '1'
Are there actually a limitation in how you order in machines list?
Changed in juju: | |
importance: | Medium → High |
milestone: | none → 2.7.4 |
Changed in juju: | |
assignee: | nobody → Harry Pidcock (hpidcock) |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
milestone: | 2.7.4 → 2.8-beta1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
probably related with this https:/ /bugs.launchpad .net/juju/ +bug/1819365