Fix quota usages update deleting same share from several API endpoints
It is possible to update quota usages multiple times sending share
deletion request to several API endpoints concurrently.
So, move quota usages update logic that is triggered by share deletion,
to DB functions level, which will be able to be executed only when
share deletion succeded. So, all concurrent requests, that failed to
delete DB record, won't commit quota usages updates.
Reviewed: https:/ /review. openstack. org/493071 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=3c596304991 927f62290fd940a 7f518ec1cae4a2
Committed: https:/
Submitter: Zuul
Branch: master
commit 3c596304991927f 62290fd940a7f51 8ec1cae4a2
Author: Valeriy Ponomaryov <email address hidden>
Date: Fri Aug 11 19:16:16 2017 +0300
Fix quota usages update deleting same share from several API endpoints
It is possible to update quota usages multiple times sending share
deletion request to several API endpoints concurrently.
So, move quota usages update logic that is triggered by share deletion,
to DB functions level, which will be able to be executed only when
share deletion succeded. So, all concurrent requests, that failed to
delete DB record, won't commit quota usages updates.
Change-Id: If7d52e08d00d43 5f2e26c30654f0d 2180b17b81a
Closes-Bug: #1707379
Closes-bug: #1707377