delete quota shouldn't delete the data of resources which in use or reserve

Bug #1246668 reported by huangtianhua
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

Set the item security_group_api=nova.

All my operations as follows:

1.Update security_groups quota for a project.
   PUT http://172.25.16.1:8774/v2/e7f9721a01a942d49262a7c016dcd290/os-quota-sets/e7f9721a01a942d49262a7c016dcd290
        {
          "quota_set":
                  {
                      "security_groups": 2
                  }
        }
2.Create two security_group for the project.
3.Update the quota to 1 of the project again.The server raises error:"Quota value 1 for security_groups are greater than already used and reserved 2".It's OK.
4.Delete the quota of this project.The quota of this project back to the default values.It's OK.
5.Update the quota to 1 of the project again.The server accept the cmd and set the security_groups quota to 1.

I think it's a bug,the project has already create two security-groups,the quota shouldn't be set less than count of using.

All other resources has the same problem.

Tags: api quotas
Changed in cloudkeep:
assignee: nobody → huangtianhua (huangtianhua)
affects: cloudkeep → nova
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/54707

Changed in nova:
status: New → In Progress
Joe Gordon (jogo)
Changed in nova:
status: In Progress → New
assignee: huangtianhua (huangtianhua) → nobody
Tracy Jones (tjones-i)
tags: added: api
Changed in nova:
status: New → Confirmed
assignee: nobody → Christopher Yeoh (cyeoh-0)
Joe Gordon (jogo)
tags: added: quotas
Claudiu Belu (cbelu)
Changed in nova:
assignee: Christopher Yeoh (cyeoh-0) → nobody
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.