When bootstrapping or deploying dont spec zone

[Charles Butler]

When bootstrapping in AWS, its a common occurrence recently that the m1.small instance type is at capacity. As select-zone has some intelligence in whats going on, this transient error could be caught and switch to a different zone.

Please evaluate the following output from testing that hilights the behavior

[Kapil Thangavelu (hazmat)]

not so much retry as not specify when not needed.

[Curtis Hovey (sinzui)]

My work around is to set --constrants mem=2G which selects from a pull that tends to be better. As Juju chooses AZ at random and rules for distributing across AZs when add-unit and ensure-ha are run, juju should make more informed choices.

[Kapil Thangavelu (hazmat)]

i suspect aws issues are related https://news.ycombinator.com/item?id=8364643.

sinzui its not about manually specifying constraints, its about our DEFAULTS which should work and they would if we didn't specify a zone when we don't need to (bootstrap and deploy).

[Kapil Thangavelu (hazmat)]

to clarify this has nothing to do with add-unit or ha which its currently tagged with.

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

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