StorPool: really detach volumes and snapshots after copying to/from an image

Bug #1978825 reported by Peter Penchev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Low
Unassigned

Bug Description

When copying a StorPool-backed volume to a Glance image (if Cinder is not used as the backing store for Glance), a temporary StorPool snapshot is created for the volume. This snapshot ought then to be deleted, but the StorPool query to delete it will always fail since it is still marked as attached to the Cinder volume host.

Similarly, when copying a Glance image to a StorPool volume (again, if Cinder is not used as the backing store for Glance), the volume itself is attached to the Cinder host and is never really detached afterwards.

Since StorPool has always transparently supported volumes and snapshots attached to multiple hosts (especially if no processes on these hosts attempt to use them, since everyone has forgotten about them), this only results in stale attachments and sometimes stale StorPool snapshots; there are no ill effects on the operation of the StorPool cluster or the Cinder volume service. Still, there is no reason for these attachments and snapshots to persist.

Tags: storpool
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/845990

Changed in cinder:
status: New → In Progress
tags: added: storpool
Changed in cinder:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.