Comment 2 for bug 1876104

Agreeing with Haw, it's not just k8s, but juju-storage usage in general.

It appears that the inclusion of --force in model destruction avoids the path of the code resulting in the following operator notification:

ubuntu@drewn3ss-bastion:~$ juju destroy-model default -y
Destroying modelERROR cannot destroy model "default"

The model has persistent storage remaining:
 3 volumes

To destroy the storage, run the destroy-model
command again with the "--destroy-storage" option.

To release the storage from Juju's management
without destroying it, use the "--release-storage"
option instead. The storage can then be imported
into another Juju model.

This is an openstack model showing the same timeout on destroy-model when --force is used:

ubuntu@drewn3ss-bastion:~$ juju destroy-model default --force --no-wait -y
Destroying model
Waiting for model to be removed, 25 machine(s), 27 application(s), 3 volume(s)..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ERROR timeout after 30m0s timeout