Bootstrapping GCE lies about the availability zone of the controller
Bug #1577614 reported by
Nate Finch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Anastasia | ||
Bug Description
When I bootstrap GCE, the bootstrap output says it's creating an instance in us-east1, but it actually gets created in us-central1.
$ juju bootstrap google google
Creating Juju controller "local.google" on google/us-east1
....
Bootstrap complete, local.google now available.
$ juju switch admin && juju status
....
ID STATE DNS INS-ID SERIES AZ
0 started 104.197.9.159 juju-34e8a09d-
| tags: | added: gce-provider status |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: ci jujuqa |
| Changed in juju-core: | |
| importance: | Medium → High |
| milestone: | none → 2.0-beta9 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Anastasia (anastasia-macmood) |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju-core: | |
| importance: | High → Critical |
| tags: | added: blocker |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| no longer affects: | juju-core/1.25 |
| Changed in juju-core: | |
| importance: | Critical → High |
| tags: | removed: blocker |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta9 → none |
| milestone: | none → 2.0-beta9 |
To post a comment you must log in.
There were 2 issues:
1. We had a hard-coded default region in the provider code.
2. We ignored region from bootstrap config parameters.
The combination of the two meant that everyone used hard-coded default region.
PR against master: https:/