Enhanced force deletion

Registered by Lisa Li on 2018-08-24

    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. This fix added a check to "force-delete" to check in nova or any existing attachments and if none exist, delete the volume.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Lisa Li
Direction:
Needs approval
Assignee:
Lisa Li
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Lisa Li on 2018-12-03

Related branches

Sprints

Whiteboard

Cinder already has a force delete volume action, so how is that insufficient today? Does it still not force the volume delete if it shows as in-use? Note that this might have been a side effect of some old bugs in nova, which should be resolved now, see https://review.openstack.org/#/c/528385/ as an example. Of course, if for some reason we have a REST API or RPC failure during the cleanup then yes you could have orphaned volumes with bad state. -- mriedem 20180828

The problem still exists in current Cinder branch:https://bugs.launchpad.net/cinder/+bug/1791213

Gerrit topic: https://review.openstack.org/#q,topic:bp/enhanced-force-deletion,n,z

Addressed by: https://review.openstack.org/600638
    Force delete invalid attached volume

Gerrit topic: https://review.openstack.org/#q,topic:bug/1791213,n,z

Addressed by: https://review.openstack.org/598067
    Enhanced force deletion

We can delete attachments at first, and then delete volumes. So set it invalid.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.