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.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #1 |
| Changed in cinder: | |
| assignee: | nobody → zhangchangfeng (changfengdaxia) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on cinder (master) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to cinder (master) | #3 |
| 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: https:/