juju destroy-model --force does not work with stale volume instances in the db
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Context
=======
version: 2.6.10
cloud: openstack train
Had already destroyed applications/
With help from babbageclunk, had to issue a series of mongo queries to delete the volume entries. After that tried destroy-model --force again but it continued to be stuck (no error this time, just stuck). Finally had to reboot the controller (all other models were working fine), and after the reboot the model was gone without further user intervention.
Ideally destroy-model --force should get rid of the model within the juju systems (especially the db), without error-prone manual intervention/db surgery and/or a controller reboot. No cloud-specific cleanup is expected in this case (OpenStack), the user would have already given up on that when invoking --force.
Command output:
ubuntu@mybox$ juju destroy-model --force mymodel
WARNING! This command will destroy the "mymodel" model.
This includes all machines, applications, data and other resources.
Continue [y/N]? y
Destroying model
Waiting for model to be removed, 6 error(s), 6 volume(
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
The following errors were encountered during destroying the model.
You can fix the problem causing the errors and run destroy-model again.
Resource Id Message
Volume 0 destroying volume: cannot release volume "a038e68b-
76/v2/58976c7d4
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
1 destroying volume: cannot release volume "68ed84a3-
76c7d41d34bce96
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
2 destroying volume: cannot release volume "0bff96c8-
76c7d41d34bce96
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
3 destroying volume: cannot release volume "96dc8380-
76c7d41d34bce96
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
4 destroying volume: cannot release volume "b38757ab-
76c7d41d34bce96
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
5 destroying volume: cannot release volume "ac575230-
76c7d41d34bce96
caused by: request (http://
tus: 401; error info: Failed: 401 error: The request you have made requires authentication.
ERROR timeout after 30m0s timeout
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: destroy-model storage |
Changed in juju: | |
milestone: | none → 2.8-next |
Changed in juju: | |
milestone: | 2.8-next → 2.8.10 |
Changed in juju: | |
milestone: | 2.8.10 → 2.8.11 |
This should be addressed in Juju 2.8.0 where --force was enhanced to also deal with state storage.
I'll mark as Incomplete and we can close unless you can reproduce with 2.8.