How To Reset Volume States
PreviousCinder Volume Operations Failing With Vmstore “NotFound” Error on Tintri BackendNextCinder Driver Fails to Decrypt Storage Passwords set via Blueprint
Last updated
Private Cloud Director block storage volumes can be in the following states: "reserved", “error”, “creating”, “deleting”, “in-use”, “attaching”, “detaching”, “error_deleting” or “maintenance”.
Sometimes the volumes might be in a state that does not reflect their present condition. For example, a failed live migration might set the volume state to "error". However, it is possible to access and edit the data inside the volume. In such a case, it becomes necessary to reset the volume state to reflect its actual condition.
Private Cloud Director Virtualization - v2025.4 and Higher
Self-Hosted Private Cloud Director Virtualization - v2025.4 and Higher
Self-Hosted Private Cloud Director Kubernetes - v2025.4 and Higher
These steps can only be run as admin. Source the RC file with the admin credentials.
$ source <RC_FILE>Get the UUID of the volume whose status that needs to be changed.
$ openstack volume listChange the status using the following command.
$ openstack volume set --state <DESIRED_STATE> <VOLUME_UUID>Verify if the volume state has changed.
Last updated
$ openstack volume show <VOLUME_UUID>