"juju kill-controller" removes controllers.yaml entry even if destroying fails
Bug #1576120 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
I just bootstrapped, and hacked the azure provider to force the Destroy method to fail, as I was testing destroying hosted models. Even though Destroy failed, the controller details were removed from the client store.
If destroying the environment fails, the controller entry should not be removed.
Revision history for this message
| Michael Foord (mfoord) wrote | #1 |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #2 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in juju-core: | |
| milestone: | 2.0-beta7 → 2.0-beta8 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta8 → none |
| milestone: | none → 2.0-beta8 |
To post a comment you must log in.
Just don't revert back to the old situation where a failed destroy could leave you in a situation where you can't kill because the model doesn't exist and can't bootstrap because it does exist...