flavor-rxtx policy not restrictive enough
Bug #1665739 reported by
Samantha Blanco
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Triaged
|
Low
|
Unassigned |
Bug Description
flavor-rxtx relies on flavor-manage, which is much more restrictive (flavor-rxtx is admin_or_owner whereas flavor-manage is admin_api). flavor-rxtx should be changed to admin_api
Changed in nova: | |
assignee: | nobody → Samantha Blanco (sblanco1) |
Changed in nova: | |
assignee: | Samantha Blanco (sblanco1) → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
assignee: | Stephen Finucane (stephenfinucane) → Samantha Blanco (sblanco1) |
Changed in nova: | |
status: | In Progress → Triaged |
assignee: | Samantha Blanco (sblanco1) → nobody |
To post a comment you must log in.
I would compare to flavor extra specs policy:
https:/ /github. com/openstack/ nova/blob/ 15.0.0. 0rc2/nova/ policies/ flavor_ extra_specs. py
Where essentially only admins can perform create/ update/ delete operations on it but admin or owner can list/show flavor extra specs.