Destroying a model fails if there is insufficient delay following creation
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
New
|
Undecided
|
Unassigned | ||
Bug Description
If a model is destroyed without a reasonable delay following creation, it results in a model that continues to exist and is not removable - the only fix appears to be restarting the controller. This is reproducible from the command line (with LXD):
$ juju add-model test-model; juju destroy-model -y test-model
Added 'test-model' model on lxd/localhost with credential 'default' for user 'admin'
Destroying model
Waiting on model to be removed...
Waiting on model to be removed...
Waiting on model to be removed...
Waiting on model to be removed...
Waiting on model to be removed...
Waiting on model to be removed...
Waiting on model to be removed...
The "Waiting on model to be removed..." line will repeat continuously - stopping the destroy and reattempting it results in the same repeated logging.
While this is an unlikely production use case, it has resulted in issues during testing. Presumably the add-model command should not return until the model has been fully created, or the destroy-model command should succeed on an incomplete model.
| Anastasia (anastasia-macmood) wrote | #1 |
This is a duplicate of bug # 1635052. It has been addressed on 2.1 tip and will be released with 2.1.0 final release.
Thank you for reporting!