Hi, Try to set first the state in error [1] openstack volume set --state error <vol id> openstack volume delete --force <vol id> Eventually, you can just do an update setting deleted=1 and it disappear but I'm not sure if something else should be updated. use cinder; update volumes set deleted='1' where id='<vol-id>'; [1] https://docs.openstack.org/api-ref/block-storage/v3/#delete-a-volume Best, M. On Mon, Jul 1, 2024 at 6:37 PM <kjme001@gmail.com> wrote:

Matteo Piccinini wrote:

...

Hello, Have you attempted to use the --force flag to force delete it? If not, I guess it is safe to try deleting it from the database using one of the methods listed here: https://cloud.garr.it/support/kb/openstack/forceDeleteVolume/ However, the instances hosted on that node In my opinion should have been removed beforehand through a node evacuation. Best, M, On Mon, Jul 1, 2024 at 6:01 PM kjme001@gmail.com wrote:

...

I have a problem with deleting a volume from OpenStack from a machine that no longer exists because it has crashed. If it executes the command: openstack volume delete volume_name receives the deleting status and the volume is not deleted, it is still in the deleting state. How can I delete such a volume? Can I remove it from the postgres database? Regards

I tried the --force switch but the volume is still in the deleting state

I have a postgresql database and this command doesn't work for me: #mysql>update volumes set deleted=1,status='deleted',deleted_at=now(),updated_at=now() where deleted=0 and id='<volumeid>';

Will there be the same command for postgresql as for mysql?

best regards and thank you for your help