[2.5] zones constraint has no effect when set as a model default
Bug #1805520 reported by
Peter Matulis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
The 'zones' constraint has no effect when set as a default at the model level. The application level default appears to work.
Model,
juju deploy apache2 --constraints zones=us-east-1b
juju set-model-
juju add-unit apache2
Both units end up in us-east-1b.
Application,
juju deploy apache2 --constraints zones=us-east-1b
juju set-constraints apache2 zones=us-east-1d
juju add-unit apache2
One unit ends up in us-east-1b and one ends up in us-east-1d.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.5.1 |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
milestone: | 2.5.8 → 2.5.9 |
To post a comment you must log in.
I didn't check when using `--constraints` during bootstrap.