public-clouds.syaml is not achieving its intended purpose and causing usability problems

[Aaron Bentley]

Yesterday's builds of Juju 2.1 do not work with the new aws regions, as seen in bug #1650105. We had similar issues with the last AWS region that we added support for.

It seems like we cannot actually expect an existing juju to work with new regions. Instead, juju must be enabled and verified to work with them.

So far, for AWS us-east-2, ca-central-1, and eu-west-2, causing juju 2.0.0 to "support" them is a usability problem. Without such support, juju will error early. With such support, juju bootstraps, but is then unable to provision new machines, which is an arguably worse outcome.

Perhaps it is not practical for old jujus to support new regions, and Juju should just use a compiled-in list of regions.

[Aaron Bentley (abentley)]

Assigning to Andrew as a proxy for assigning to the tech board.

[Anastasia (anastasia-macmood)]

Marking as Won't Fix for 2.0 as we are not planning another release in 2.0.x.
Marking as Wont' Fix for 2.1 as the scope of 2.1.0 (final) release is already defined.

Leaving this bug in 2.2.x in the spirit of coming up with a feasible long-term solution in the future release.

[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.