any value for quota project id can be updated
Bug #1037373 reported by
Zhou ShaoYu
This bug report is a duplicate of:
Bug #1118066: Nova should confirm quota requests against Keystone.
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Eoghan Glynn |
Bug Description
no check for whether tenant id exists,like "axx" in the request url followed
curl -X "PUT" -H "x-auth-
Changed in nova: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
The main issues here are:
(a) DB pollution with the quota bounding a non-existent project that never gets enforced
(b) the lack of feedback when a user fat-fingers the project ID in a call to nova-manage setting the quota
Other than that, there are no ill-effects that I can see, but it certainly should be fixed in any case for Folsom.