barbican client doesn't use keystone correctly
Bug #1491257 reported by
yuanying
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
High
|
yuanying |
Bug Description
In magnum.
directly, but `keystone().client` is better to use.
Because..
* `keystone(
* `keystone().client` can return keystone client which has admin privilege.
Changed in magnum: | |
assignee: | nobody → yuanying (ootsuka) |
importance: | Undecided → Medium |
importance: | Medium → High |
Changed in magnum: | |
status: | New → In Progress |
Changed in magnum: | |
milestone: | none → mitaka-2 |
status: | Fix Committed → Fix Released |
Changed in magnum: | |
milestone: | mitaka-2 → mitaka-1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/219579 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=77d1e32c946 5d63965109a3cbe fc93f6aaf54052
Committed: https:/
Submitter: Jenkins
Branch: master
commit 77d1e32c9465d63 965109a3cbefc93 f6aaf54052
Author: OTSUKA, Yuanying <email address hidden>
Date: Wed Sep 2 13:24:45 2015 +0900
Fix keystone client usage in barbican client
In magnum. common. clients, barbican client uses )._client` directly, but `keystone().client`
`keystone(
is better. Because, keystone()._client is None is it
is not loaded.
This fixes it.
Closes-Bug: #1491257 3756ea4ed2f9647 51d1c2da43f
Change-Id: I3771ebef9c2a1d