quota-update should error out if input provided is wrong tenant id
Bug #1307378 reported by
Tushar Bankar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
Won't Fix
|
Undecided
|
Harshada Mangesh Kakad | ||
Bug Description
manila quota-update wrong-tenant --gigabytes 2
manila returns 200 (OK).
It is expected to return 404 if tenant does not exists.
| Changed in manila: | |
| assignee: | nobody → Tushar Bankar (tushar-bankar) |
| tags: | added: izeltech |
| Changed in manila: | |
| assignee: | Tushar Bankar (tushar-bankar) → nobody |
| Changed in manila: | |
| assignee: | nobody → Harshada Mangesh Kakad (harshada-kakad) |
Revision history for this message
| Valeriy Ponomaryov (vponomaryov) wrote | #1 |
| Changed in manila: | |
| status: | New → Won't Fix |
To post a comment you must log in.
Set it as "won't fix" because:
Manila has default values for all quotas, independently from tenants/projects in auth service.
When quota is updated manila creates record in database.
So, when we request quota for tenant, even not existent, quota will be calculated correctly - if no record in DB, assumed default quota without check for existance of tenant/project. Same situation for all operations with quotas.
In conclusion: all bugs, related to such kind of quotas behavior should be closed as 'won't fix'.