Blocking endless loop when destroying models
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Juju version: 3.2-rc1. Right now using the corresponding branch from GitHub.
When destroying a model with charms in a with storage in a pending stage, juju falls into an endless loop until reaching the 30 minutes timeout.
juju add-model removeme
Added 'removeme' model on localhost/localhost with credential 'localhost' for user 'admin'
juju deploy ubuntu --base ubuntu@22.04
Located charm "ubuntu" in charm-hub, revision 22
Deploying "ubuntu" from charm-hub charm "ubuntu", revision 22 in channel stable on ubuntu@22.04/stable
juju destroy-model removeme
WARNING This command will destroy the "removeme" model and all its resources
- 1 machine will be destroyed
- machine list: "0 ()"
- 1 application will be removed
- application list: "ubuntu"
- 1 filesystem and 0 volume will be destroyed
To continue, enter the name of the model to be destroyed: removeme
Destroying model
Waiting for model to be removed, 1 machine(s), 1 application(s), 1 filesystems(
This will continue for 30 minutes until reaching the timeout. In the controller logs I see:
juju debug-log -m controller
...
machine-0: 12:59:22 WARNING juju.state cleanup failed in model eee33fcb-
machine-0: 12:59:52 WARNING juju.state cleanup failed in model eee33fcb-
machine-0: 13:00:05 ERROR juju.worker.
machine-0: 13:00:22 WARNING juju.state cleanup failed in model eee33fcb-
....
tags: | added: deploy destroy-model storage |
Changed in juju: | |
milestone: | none → 3.2-rc1 |
status: | New → Triaged |
Changed in juju: | |
milestone: | 3.2-rc1 → none |
If storage is not yet attached, the unit will block and not progress any subsequent hooks. You either need to wait for storage to be attached or use force.