gce provider should stop using deprecated zone europe-west1-a
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
High
|
Wayne Witzel III | ||
| | 1.23 |
High
|
Wayne Witzel III | ||
Bug Description
According to the release notes (https:/
| Changed in juju-core: | |
| milestone: | 1.23-beta3 → none |
| milestone: | none → 1.24-alpha1 |
| Eric Snow (ericsnowcurrently) wrote : | #1 |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
| Changed in juju-core: | |
| milestone: | 1.24-alpha1 → none |
| Changed in juju-core: | |
| status: | Won't Fix → Triaged |
| milestone: | none → 1.24-alpha1 |
| Dan Watkins (daniel-thewatkins) wrote : | #2 |
The latest adamisrael/
It looks like this is probably because it is still being returned from the API (with deprecation information), despite it being actually gone.
| Eric Snow (ericsnowcurrently) wrote : | #3 |
The provider should be using the deprecation information from the GCE API:
https:/
If we don't fix this, future deprecated zones will break the provider in the same way.
| Changed in juju-core: | |
| assignee: | nobody → Wayne Witzel III (wwitzel3) |
| Changed in juju-core: | |
| status: | Triaged → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |


Yeah, the list of zones is queried via the GCE API at run-time. So you're right. :) Given the release timeframe for 1.23 we don't need to worry about "europe-west1-a". However, I'll make sure there is a brief mention of it in the release notes.