placement keystonemiddleware_authtoken ignores OS_PLACEMENT_CONFIG_DIR
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Chris Dent |
Bug Description
In placement master, late November 2017, the deploy.py file is responsible for building the WSGI middleware stack, including loading the keystonemiddleware.
{}, oslo_config_
This mode of loading means that the middleware itself is responsible for finding and reading the project conf file (nova.conf for now).
Whereas the general the conf loading done in wsgi.py is aware of an OS_PLACEMENT_
This can lead to some pretty confusing situations where custom config, for things like the database, from custom locations are visible in the placement service, but authtoken config is not.
Only after pulling all hair from head does it become clear what's happening.
So we should fix that. It _may_ be as simple as adding similar file handling as used in wsgi.py, but it's not clear if the arg will get passed through. Further experimentation required.
tags: | added: pike-backport-potential |
Changed in nova: | |
importance: | Undecided → Low |
Set the status to "In-Progress" because this report has an assignee.