When placement accesses keystone API with keystone_middleware,the config of keystone_authtoken in placement.conf does not take effect.
Bug #2071904 reported by
yyh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
placement |
New
|
Undecided
|
Unassigned |
Bug Description
As mentioned in the title, I found that placement does not use cache token when accessing keystone api,resulting in slow response of the keystone interfaces.In fact, I found the keystone_authtoken config of placement was not transferred to keystone_
I tried to change one line of code in placement/wsgi.py +124 to “config = cfg.CONF”,which effectively passed the configuration to keystone_middleware and used memcache.
Please help to confirm if it is a bug,thanks.
placement version:2.0.1
keystone middleware version:7.0.2