Unable to start placement wsgi app without conf file

Bug #1802925 reported by Chris Dent
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Chris Dent

Bug Description

oslo_config allows configuration to come from the process environment (e.g., OS_PLACEMENT_DATABASE__CONNECTION). This was developed to allow services that use oslo_config to hosted within immutable containers.

However, as currently written, the placement-wsgi app (in both nova and placement) cannot start if there isn't at least an empty placement.conf, either in /etc/placement or in the directory defined by OS_PLACEMENT_CONFIG_DIR.

It's easy enough to work around this: set the empty file in the container and forget about it.

In placement/wsgi.py:

    conf.CONF(argv[1:], project='placement',
              version=version_info.version_string(),
              default_config_files=default_config_files)

is the call that causes the problem, because default_config_files is always non-None, even when the original default is being used. We can fix this by only setting the value when a non default is being used.

(This is possible now that placement is placement, not nova).

Tags: placement
Matt Riedemann (mriedem)
Changed in nova:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Chris Dent (cdent) wrote :

in progress with https://review.openstack.org/#/c/619049/

not sure why things aren't being automatic

Changed in nova:
status: Triaged → In Progress
assignee: nobody → Chris Dent (cdent)
Chris Dent (cdent)
Changed in nova:
status: In Progress → Fix Committed
Changed in nova:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.