Since this is being handled by the v3-api-policy blueprint and being
tracked by that blueprint, I'm closing this bug report
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1240831
Title:
Changing policy.json is invalid for creating an aggregate
Status in OpenStack Compute (Nova):
Invalid
Bug description:
In default, Aggregate actions require the admin-user to operate.
In order to give rights to normal-user, I change it in the policy.json
, like this:
from
"compute_extension:aggregates": "rule:admin_api",
to
"compute_extension:aggregates": "",
But the operation result is also rejected.
----------------
I check the codes in Nova, the fault dues to def
require_admin_context() in /nova/db/sqlalchemy/api.py.
That means Nova has checked the policy of one API twice.
So why twice? The policy has already checked in the api-layer.
That cause the problem happens~
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1240831/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
