RFE: Provide an admin API to query quotas for all user in a project

Bug #1868088 reported by Douglas Viroel
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
In Progress
Matheus Andrade

Bug Description

Admins might face some hard times when dealing with user quotas for resources.
Currently, Manila accepts quotas sets for any user-id and this might lead to unwanted DB entries if the admin enters, by mistake, an invalid user-id. At the end, this will affect the total project quota that will consider all user quotas.
This is a request for implement an new API to query all user's quotas associated to an project. In this way, admins will be able to unwanted entries using quota-delete operations.

How to reproduce the behavior:
1. Create a quota for user-A using its user-id (correct way)
$ manila quota-update 1fc7b1ed9a7d4b4ab6eb66dc09fec97b --user-id f6fd7e75ff994fb0b7b847932effa25f --shares 7
2. Try to update user-A, and provide a different user-id, by mistake:
$ manila quota-update 1fc7b1ed9a7d4b4ab6eb66dc09fec97b --user-id f6fd7e75ff994fb0b7b847932effa25f] --shares 8
3. Try to update project quot:
$ manila quota-update 1fc7b1ed9a7d4b4ab6eb66dc09fec97b --shares 10
ERROR: Quota limit must be greater than 15. (HTTP 400)

The database has both entries and there is no easy way for admins to retrieve this information.

Tags: quotas
Douglas Viroel (dviroel)
description: updated
Vida Haririan (vhariria)
Changed in manila:
milestone: none → victoria-1
importance: Undecided → Low
Revision history for this message
Vida Haririan (vhariria) wrote :
Douglas Viroel (dviroel)
Changed in manila:
assignee: nobody → Carlos Eduardo (silvacarlose)
Changed in manila:
milestone: victoria-1 → victoria-2
Changed in manila:
milestone: victoria-2 → victoria-3
Revision history for this message
Goutham Pacha Ravi (gouthamr) wrote :

This is an API change; it needs to be micro-versioned and cannot be back ported - I'll leave this around as a tracker; but since changes weren't targeted before feature freeze in the Victoria cycle, we can pick this up in the Wallaby development cycle.

Changed in manila:
milestone: victoria-3 → victoria-rc1
milestone: victoria-rc1 → wallaby-3
Changed in manila:
milestone: wallaby-3 → none
milestone: none → xena-1
Changed in manila:
milestone: xena-1 → xena-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/manila/+/807780

Changed in manila:
status: New → In Progress
Changed in manila:
assignee: Carlos Eduardo (silvacarlose) → Luisa (rfluisa)
milestone: xena-2 → yoga-1
Changed in manila:
milestone: yoga-1 → yoga-2
Changed in manila:
milestone: yoga-2 → yoga-3
Changed in manila:
milestone: yoga-3 → zed-1
Changed in manila:
assignee: Luisa (rfluisa) → Matheus Andrade (matheusandrade777)
Changed in manila:
milestone: zed-1 → zed-2
Changed in manila:
milestone: zed-2 → zed-3
Changed in manila:
milestone: zed-3 → antelope-3
Changed in manila:
milestone: antelope-3 → antelope-rc1
Changed in manila:
milestone: antelope-rc1 → bobcat-1
Changed in manila:
milestone: bobcat-1 → bobcat-rc1
milestone: bobcat-rc1 → bobcat-3
Changed in manila:
milestone: bobcat-3 → bobcat-rc1
Changed in manila:
milestone: bobcat-rc1 → caracal-1
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.