Better messages around destroy / kill-controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
The output during destroy-controller is too verbose and hides the error message. For instance, I got:
juju destroy-controller b3aws
WARNING! This command will destroy the "local.b3aws" controller.
This includes all machines, services, data and other resources.
Continue [y/N]? y
ERROR failed to destroy controller "local.b3aws"
If the controller is unusable, then you may run
juju kill-controller
to forcibly destroy the controller. Upon doing so, review
your model provider console for any resources that need
to be cleaned up.
ERROR cannot destroy controller: controller model cannot be destroyed before all other models are destroyed
I think the kill-controller note should be in help only and not during the output here so that this can be reduced and the "ERROR" is more prominent in the output.
juju destroy-controller b3aws
WARNING! This command will destroy the "local.b3aws" controller.
This includes all machines, services, data and other resources.
Continue [y/N]? y
ERROR failed to destroy controller "local.b3aws": controller model cannot be destroyed before all other models are destroyed
Changed in juju-core: | |
milestone: | none → 2.0.1 |
summary: |
- juju destroy-controller hides error message when multiple models exist + Better messages around destroy / kill-controller |
tags: | added: usability |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.1 → none |
milestone: | none → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
tags: | added: teardown |
Changed in juju: | |
status: | Triaged → Fix Committed |
milestone: | none → 2.6-rc2 |
I would suggest that we do mention 'kill-controller' for the cases where we fail to connect to the controller.