Quotas should not be updated to a value lower than current usage
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
wanghao |
Bug Description
Cinder/Neutron now doesn't check the existing reousrces when user lower the quota sets.
It will bring some confusion to end user.
Simple steps to test:
Step1: Create 3 volumes successfully and the quota limit for volume is 10(default).
Step2: Update the quota set, lower the volume limit to 1. The update operation will be successfully too.
Step3: Create one more volume and get failed since "Maximum number of volumes allowed (1) exceeded".
I knew we have discussed this 'bug' and I understood guys' point about this feature.
But undeniably, I also has received some complains from end users, they feel confusion why the existing resources more than the limits of quota but they can't create any resources any more. So,this maybe is inappropriate as 'bug fix', just want to optimize this API.
Changed in neutron: | |
assignee: | nobody → shihanzhang (shihanzhang) |
Changed in cinder: | |
assignee: | nobody → shihanzhang (shihanzhang) |
Changed in cinder: | |
assignee: | shihanzhang (shihanzhang) → ling-yun (zengyunling) |
Changed in cinder: | |
status: | Invalid → In Progress |
summary: |
- the problem of updating quota + Quotas should not be updated to a value lower than current usage |
Changed in cinder: | |
assignee: | ling-yun (zengyunling) → wanghao (wanghao749) |
description: | updated |
Changed in cinder: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-3 → 7.0.0 |
no longer affects: | neutron |
Can you please be more descriptive on how you're updating the quota?