cannot destroy rc2 aws controller with rc3 client
Bug #1631216 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
The AWS endpoints in public-clouds.yaml all changed between rc2 and rc3. In rc2 they were ignored, and they were all wrong. In rc3 we corrected them and started using them.
However, if you bootstrapped rc2, the wrong endpoint is cached in bootstra-
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.