Unable to bootstrap on cn-north-1
Bug #1415693 reported by
Michael Nelson
on 2015-01-29
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
High
|
Katherine Cox-Buday | ||
Bug Description
When bootstrapping using aws cn-north-1, I get the error:
2015-01-28 02:00:39 ERROR juju.cmd supercommand.go:323 cannot determine if environment is already bootstrapped.: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
It's worth noting that accessing cn-north-1 via the awscli works without issue (as far as I tested): https:/
More details: https:/
Note: I had already created a specific goamz git issue [1], but axw mentioned here is where bugs are tracked for releases.
| Michael Nelson (michael.nelson) wrote : | #1 |
Curtis Hovey (sinzui)
on 2015-01-29
| tags: | added: bootstrap ec2-provider |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.23 |
Curtis Hovey (sinzui)
on 2015-01-29
| tags: | added: online-services |
Katherine Cox-Buday (cox-katherine-e)
on 2015-02-09
| Changed in juju-core: | |
| assignee: | nobody → Katherine Cox-Buday (cox-katherine-e) |
Katherine Cox-Buday (cox-katherine-e)
on 2015-02-11
| Changed in juju-core: | |
| status: | Triaged → In Progress |
Fix is under review: https:/
Ian Booth (wallyworld)
on 2015-03-03
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
Curtis Hovey (sinzui)
on 2015-03-09
| Changed in juju-core: | |
| milestone: | 1.23 → 1.23-beta1 |
Curtis Hovey (sinzui)
on 2015-03-20
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Also, I'm keen to know whether, if and when this is fixed, it would be included in an update to the trusty release (our IS generally use stable juju releases only so that upgrading the environment is supported, getting an exception would require work that I can organise in advance).