timeouts when destroying models
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Confirmed
|
Low
|
Unassigned |
Bug Description
Since upgrading our CI controller to 2.8.0 we're seeing lots of models stuck in "destroying" state:
Destroying Model charm-testing-
Destroying model
Waiting for model to be removed, 3 machine(s), 2 application(
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
The models appear to have no machines, cores or units associated with them any more, but are still marked as "destroying". Interestingly, when re-running "juju destroy-model" on such a model, it begins with "Waiting for model to be removed, 3 machine(s), 2 application(s)" again, even though the output from "juju models" shows 0 machines, cores and units.
The client is 2.8.0-xenial-amd64.
Related branches
- Stuart Bishop (community): Approve
- Mojo Maintainers: Pending requested
-
Diff: 55 lines (+15/-3)3 files modifiedcontrib/jenkins/juju2-run-jenkins-job-bzr-lxd-spec (+5/-1)
contrib/jenkins/juju2-run-jenkins-job-bzr-spec (+5/-1)
contrib/jenkins/juju2-run-jenkins-job-git-spec (+5/-1)
It seems to work okay with --force, fwiw:
$ juju destroy-model --force charm-testing- cassandra- bionic- 137 testing- cassandra- bionic- 137" model.
WARNING! This command will destroy the "charm-
This includes all machines, applications, data and other resources.
Continue [y/N]? y
Destroying model
Waiting for model to be removed, 3 machine(s), 2 application(s).....
Waiting for model to be removed, 3 machine(s).....
Waiting for model to be removed, 2 machine(s).....
Waiting for model to be removed, 1 machine(s).....
Waiting for model to be removed....
Model destroyed.