How to resolve "removing volume 0: volume is not dead"

juju
1

We have a lxd-controller that complains in the logsink.log about a cleanup failed:

logsink.log

ee22bb90-3bbf-4898-8b6a-80c28b3c6a27: machine-0 2024-07-05 12:49:36 WARNING juju.state cleanup.go:247 cleanup failed in model 9e798e33-9b8f-4dfc-8991-7c984eaa455a for forceStorage("9e798e33-9b8f-4dfc-8991-7c984eaa455a"): removing volume 0: volume is not dead

I can’t investigate the model, since it existed in an old k8s cloud which isn’t there any-more.


juju show-model 9e798e33-9b8f-4dfc-8991-7c984eaa455a
{}
ERROR accessing model environment: unable to determine legacy status for namespace "cos": Get "https://192.168.113.2:16443/api/v1/namespaces/cos": dial tcp 192.168.113.2:16443: i/o timeout

Is there a way to clean this up since its bloating the logs alot?

@marcus

2

If you can connect to Mongo and locate the offending record in the volumes collection, manually set its life value to 2 (dead).