public cloud data out of sync
Bug #1769879 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Unassigned |
Bug Description
On a fresh juju 2.4 install, running the first command syncs public cloud data. This is the result:
deleted cloud region:
- aws/eu-west-3
- google/europe-west2
- google/europe-west3
- google/
- google/us-east4
There's a mismatch between what we ship and what's in public-clouds.yaml. This needs to be fixed before release, and 2.3 also needs to be checked.
Changed in juju: | |
milestone: | 2.4-beta2 → none |
Changed in juju: | |
milestone: | none → 2.4-rc1 |
no longer affects: | juju/2.3 |
Changed in juju: | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Without digging too deeply, it may be that just the public-clouds.yaml needs to be updated and not juju itself. But we should check that 2.3 and 2.4 ship with consistent cloud definitions.