concurrent deletion for volumes which host is None cause wrong quota deduction.
Bug #1733179 reported by
zhangchangfeng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
In Progress
|
Undecided
|
Jay Bryant |
Bug Description
The volume's host maybe None in some situation, such as the wrong volume_backend_name configuration or the capacity of the volume backend.
When delete such a volume in a very short time twice, the two deletion request will both successful, and the gigabytes quota will be deduction twice, this will quite vulnerable.
Changed in cinder: | |
status: | In Progress → Incomplete |
status: | Incomplete → In Progress |
Changed in cinder: | |
assignee: | zhangchangfeng (changfengdaxia) → Sean McGinnis (sean-mcginnis) |
Changed in cinder: | |
assignee: | Sean McGinnis (sean-mcginnis) → Jay Bryant (jsbryant) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/521364
Review: https:/