[2.5] zones constraint has no effect when set as a model default

[Peter Matulis]

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-constraints zones=us-east-1d
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.

[Peter Matulis (petermatulis)]

I didn't check when using `--constraints` during bootstrap.

[Anastasia (anastasia-macmood)]

Removing from a milestone as this work will not be done in 2.5 series.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.