Horizon overwrites existing roles when saving project membership
Bug #1081374 reported by
Adam Greene
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
Kieran Spear |
Bug Description
Using the keystone CLI, add a user to 2 roles in a given Project/Tenant. MySQL backend will show both roles:
{"roles": ["70b6103d95e94
Using the Modify Users interface under Projects, you will only see one of the two roles. If you select Save, only one role is saved to the database.
{"roles": ["70b6103d95e94
This applies no matter which user you are modifying. i.e., if you change the role on a second user, any users with multiple roles will end up with a single role.
Changed in horizon: | |
milestone: | grizzly-2 → grizzly-3 |
Changed in horizon: | |
milestone: | grizzly-3 → none |
Changed in horizon: | |
assignee: | nobody → Kieran Spear (kspear) |
Changed in horizon: | |
milestone: | none → grizzly-rc1 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
There are two distinct problems here:
1. Horizon doesn't support assigning multiple roles to a user on a project. That should probably be a blueprint since that's feature territory, not a bug.
2. The current implementation of the project membership interface (where roles are controlled) re-saves *all* the users in the project even if they're not modified, and that's not a good behavior. I'll take that as a bug.