do all validation before "to continue" when destroying a controller

Bug #1999666 reported by Heather Lanigan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Vitaly Antonenko

Bug Description

$ juju destroy-controller test
WARNING! This command with destroy the "test" controller and all it's resources:
 - 2 model(s) will be destroyed;
  - model list: "five, marie";
 - 4 machine(s) will be destroyed;
 - 4 application(s) will be removed;
 - 0 filesystem(s) and 0 volume(s) will be destroyed.
To continue, enter the name of the controller to be destroyed: test
Destroying controller
ERROR cannot destroy controller "test"

The controller has live models. If you want
to destroy all models in the controller,
run this command again with the --destroy-all-models
option.

Models:
 admin/five (alive), 2 machines, 2 applications
 admin/marie (alive), 2 machines, 2 applications

Very annoying to agree to destroying the models and continue, then still have it fail from a missing flag to destroy the models. Let's reorder the logic here.

Revision history for this message
Vitaly Antonenko (anvial) wrote :

We changed this logic in 3.0.

The code is already landed: https://github.com/juju/juju/pull/14977

Changed in juju:
milestone: 3.1-beta1 → 3.0.3
status: Triaged → Fix Committed
Jack Shaw (jack-shaw)
Changed in juju:
assignee: Jack Shaw (jack-shaw) → nobody
assignee: nobody → Vitaly Antonenko (anvial)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.