Quickstart claims juju doesn't support all Joyent regions
Bug #1488196 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
Triaged
|
High
|
Unassigned | ||
Bug Description
Joyent had an outage affecting us-east-1 and us-west-1. We switched our Joyent testing environments to use us-east-3 per the advice of Joyent. All Juju jobs passed accept for the quickstart job, which claimed Juju doesn't support us-east-3. I hacked the juju-quickstart on the machine to allow the job to run.
While the immediate fix for this issue would be to add the missing regions, I question why quickstart wants to check the regions. Clouds change everyday, and Juju supports the changes most of the time. I don't think the juju-quickstart team wants to monitor announcements for new region from all the clouds to prevent the code from bit rotting.
Related branches
lp:~sinzui/juju-quickstart/all-regions
- Madison Scott-Clary (community): Approve (code)
-
Diff: 31 lines (+7/-1)1 file modifiedquickstart/models/envs.py (+7/-1)
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
To post a comment you must log in.
We track it so that when editing your environments.yaml we give you selectable options to prevent typos in the config preventing things working.
We'll look at what error juju spits out these days about the region and if it's clear then we might skip that sanity check but still provide the regions listing for helping out the environment.yaml editing.