← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1696830] Re: nova-placement-api default config files is too strict

 

It looks like there's more to this. From what I can tell, the placement
api config doesn't actually make its way through from the placement wsgi
script to keystonemiddleware via OS_PLACEMENT_CONFIG_DIR or via my
attempt to fix above by passing sys.argv. While setting debug=true makes
it look like the config gets applied, it doesn't actually get passed
along.

See nova/api/openstack/placement/deploy.py:

# Do not provide global conf to middleware here.
        auth_middleware = auth_token.filter_factory(
            {}, oslo_config_project=project_name)

I think that results in the ConfigOpts class of oslo_config having to
call find_config_files() and find_config_dirs() which will search
standard config locations (~/.nova, ~/, /etc/nova, /etc) for config.

For the nova snap package, the config will either be in
/snap/nova/current/etc/nova/ or /var/snap/nova/common/etc/nova, neither
of which would be in oslo_config's standard search paths.

It seems that this should be fixed in nova, but oslo_config could also
be updated to be a bit more flexible in their standard search paths,
perhaps with snap package directories or via environment variables.

** Also affects: oslo.config
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1696830

Title:
  nova-placement-api default config files is too strict

Status in OpenStack Compute (nova):
  Confirmed
Status in oslo.config:
  New
Status in Nova Snap:
  New

Bug description:
  If nova.conf doesn't exist in the typical location of
  /etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova-
  placement-api's wsgi application will fail. In our case with the
  OpenStack snap, we have two possible paths we may pick nova.conf up
  from, based on what --config-file specifies. I think the right answer
  here is to be a bit more flexible and not set the default config file
  if it's path doesn't exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1696830/+subscriptions


References