yahoo-eng-team team mailing list archive

[OpenStack Infra <1696830@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/474212
Committed: https://git.openstack.org/cgit/openstack/oslo.config/commit/?id=21e70e28b3015c1619dacfad8a2218b09e8109ec
Submitter: Jenkins
Branch:    master

commit 21e70e28b3015c1619dacfad8a2218b09e8109ec
Author: Corey Bryant <corey.bryant@xxxxxxxxxxxxx>
Date:   Wed Jun 14 09:57:23 2017 -0400

    Add snap package paths to default config dirs
    
    With snap packaging (see snapcraft.io) the package is installed into a
    read-only squashfs filesystem, which includes the default config. For
    example, $SNAP/etc/nova/nova.conf. To override the defaults, a separate
    writable directory is used, and this directory is also unique to the snap.
    For example, either $SNAP_COMMON/etc/nova/nova.conf, or
    $SNAP_COMMON/etc/nova/nova.conf.d/ can be used to override config.
    
    This patch adds these snap directories to the default config paths where
    oslo looks for config.
    
    For more details on $SNAP and $SNAP_COMMON please refer to
    https://snapcraft.io/docs/reference/env.
    
    Change-Id: I83627e0f215382aedc7b32163e0303b39e8bccf8
    Closes-Bug: 1696830


** Changed in: oslo.config
       Status: In Progress => Fix Released

-- 
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:
  Fix Released
Status in Glance Snap:
  New
Status in Keystone Snap:
  New
Status in Neutron Snap:
  New
Status in Nova Snap:
  In Progress
Status in Nova Hypervisor 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