Can't delete invalid attached volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Won't Fix
|
Undecided
|
Liang Fang |
Bug Description
In case of a failure in communication between Nova and cinder, an instance can be deleted, but the attached volume is not properly marked as detached and cannot be deleted.
Environment:
Master branch (5df39425399abb
Test steps:
1. Create a volume and attach it to an instance.
2. Stop the cinder volume service and cinder schedule service. (To simulate disconnection between nova and cinder.)
3. Delete the VM. The VM is deleted successfully.
3. Start the cinder volume service and cinder schedule service
4. The volume status is just like the step 2 above, and the force-deletion is not allowed.
Detailed steps:
$ openstack volume list
+------
| ID | Name | Status | Size | Attached to |
+------
| 3b73e216-
+------
$ nova show 3b73e216-
ERROR (CommandError): No server with a name or ID of '3b73e216-
$ openstack volume delete --force 3b73e216-
Failed to delete volume with name or ID '3b73e216-
1 of 1 volumes failed to delete.
Changed in cinder: | |
assignee: | nobody → Lisa Li (lisali) |
Changed in cinder: | |
assignee: | Lisa Li (lisali) → Liang Fang (liangfang) |
Changed in cinder: | |
status: | New → In Progress |
As discussed in the PTG, there is no need to modify the force delete operation.
You can delete the volume if you first detach it using the new Attach API [1].
[1]: https:/ /developer. openstack. org/api- ref/block- storage/ v3/#attachments