destroy-controller blocks when you've not removed an empty default model
Bug #1563615 reported by
Richard Harding
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
destroy-controller should be more intelligent to keep users from using kill-controller by default.
If the only model there is the 'default' one and it's empty, it's safe to destroy the controller. This helps enable a clean
juju bootstrap
juju destroy-controller
without hitting a blocking message about the default model not being removed. Currently you have to know and remember to do:
juju bootstrap
juju remove-model default
juju destroy-controller
| tags: | added: juju-release-support |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in juju-core: | |
| milestone: | none → 2.0-beta4 |
| Changed in juju-core: | |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| status: | Triaged → In Progress |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| 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-beta4 → none |
| milestone: | none → 2.0-beta4 |
To post a comment you must log in.
https:/