Merge lp:~gandelman-a/charms/precise/keystone/fix-grant-role into lp:~charmers/charms/precise/keystone/trunk
Proposed by
Adam Gandelman
Status: | Merged |
---|---|
Approved by: | Mark Mims |
Approved revision: | 32 |
Merge reported by: | Adam Gandelman |
Merged at revision: | not available |
Proposed branch: | lp:~gandelman-a/charms/precise/keystone/fix-grant-role |
Merge into: | lp:~charmers/charms/precise/keystone/trunk |
Diff against target: |
37 lines (+13/-5) 2 files modified
hooks/utils.py (+12/-4) revision (+1/-1) |
To merge this branch: | bzr merge lp:~gandelman-a/charms/precise/keystone/fix-grant-role |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Mark Mims (community) | Approve | ||
Review via email: mp+118836@code.launchpad.net |
Description of the change
Avoids an exception that is raised when attempting to redefine an already existing association between a role and user+tenant. This makes utils.grant_role() check for the association before adding it.
This only triggers when using this charm to deploy Folsom, the exception is not raised in Essex. However, I'd prefer to fix in the Precise branch since:
- the functionality is there.
- its best practice.
- minimize the delta between the precise/keystone and quantal/keystone (when it opens)
To post a comment you must log in.
lgtm