Doing volume force delete operation on volume-A will change volume-A's
status to 'deleted', so all related data about volume-A should be deleted.
Now current version's volume_destroy function doesn't delete related data
of volume transfer. If there is volume transfer about volume-A, first do
force delete operation on volume A, and thus the volume-A's transfer data
would be residual. So remove the related data of volume transfer in
volume_destroy function.
Change-Id: Id80a6e0cc061fccb02af60706244be043abdd72d
Closes-Bug: #1270785
(cherry picked from commit 19d8040d61d453ec3916d74c628189ca0b54ac59)
Reviewed: https:/ /review. openstack. org/72249 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=42e28055aaf 3868cc8bd2730e0 840e872012abc0
Committed: https:/
Submitter: Jenkins
Branch: stable/havana
commit 42e28055aaf3868 cc8bd2730e0840e 872012abc0
Author: ling-yun <email address hidden>
Date: Mon Jan 20 18:48:43 2014 +0800
Delete volume transfer in volume_destroy function
Doing volume force delete operation on volume-A will change volume-A's
status to 'deleted', so all related data about volume-A should be deleted.
Now current version's volume_destroy function doesn't delete related data
of volume transfer. If there is volume transfer about volume-A, first do
force delete operation on volume A, and thus the volume-A's transfer data
would be residual. So remove the related data of volume transfer in
volume_destroy function.
Change-Id: Id80a6e0cc061fc cb02af60706244b e043abdd72d c3916d74c628189 ca0b54ac59)
Closes-Bug: #1270785
(cherry picked from commit 19d8040d61d453e