GlusterFS: Handle deletion of snapshot with no backing file
If a glusterfs volume is in-use, nova is called to delete a
volume snapshot. It is possible for a timeout to occur, since
cinder is polling for nova task progress. In such case, a
GlusterfsException is thrown, but nova continues to process the
snapshot delete and commits the changes. Cinder is not aware of
this, and the actual snapshot entry in cinder is prevented from
being deleted, since no backing file exists for the out-of-sync
snapshot. This patch allows a snapshot with no backing file to
be deleted from cinder and updates the volume info file.
Reviewed: https:/ /review. openstack. org/96340 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=3fd0a403b26 88a52603accb9cc 530a6b0ccad066
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3fd0a403b2688a5 2603accb9cc530a 6b0ccad066
Author: Thang Pham <email address hidden>
Date: Wed May 28 23:07:49 2014 -0400
GlusterFS: Handle deletion of snapshot with no backing file
If a glusterfs volume is in-use, nova is called to delete a ception is thrown, but nova continues to process the
volume snapshot. It is possible for a timeout to occur, since
cinder is polling for nova task progress. In such case, a
GlusterfsEx
snapshot delete and commits the changes. Cinder is not aware of
this, and the actual snapshot entry in cinder is prevented from
being deleted, since no backing file exists for the out-of-sync
snapshot. This patch allows a snapshot with no backing file to
be deleted from cinder and updates the volume info file.
Change-Id: I83c8a7242199ed bfd1897297589ac 7deb42c5865
Closes-Bug: #1311182