How To Delete a Volume Stuck in "Reserved" State
Problem
Users may encounter situations where a block storage volume cannot be deleted because it is stuck in the reserved state.
This condition usually occurs when a volume operation (such as attach, detach, or delete) was initiated but did not complete successfully. As a result, the volume remains marked as reserved in the database even though it is not actively attached to any instance.
When a volume is in this state, attempts to delete it will fail until the state is manually reset.
Example output showing a volume stuck in reserved state:
The volume service list has multiple volumes in down state:
$ openstack volume show <VOLUME_UUID>
+--------------------------------+-------------------------------+
| Field | Value |
+--------------------------------+-------------------------------+
| id | [VOLUME_UUID] |
| status | reserved |
| size | [VOLUME_SIZE] |
| attachments | [] |
| multiattach | False |
| name | [VOLUME_NAME] |
| bootable | false |
| created_at | [CREATION_TIMESTAMP |
+--------------------------------+-------------------------------+Environment
Private Cloud Director Virtualization - v2025.10 and Higher
Self-Hosted Private Cloud Director Virtualization - v2025.10 and Higher
Procedure
These steps can only be run as admin. Source the RC file with the admin credentials.
Identify the Volume - Retrieve the volume UUID.
Reset the Volume state to Available:
Delete the Volume:
Validation
Verify that the volume has been successfully deleted.
If the volume is deleted successfully, the command should return a message similar to:
Last updated
