[Bug 1550188] Re: oslo_concurrency.lock_path: sensible default value is missing

[James Page]

Couple of ideas on resolution:

1) update oslo_concurrency to fallback to '$state_path/lock' if
OSLO_LOCK_PATH is not set

2) set OSLO_LOCK_PATH in agent configurations across the package.

3) patch the neutron.conf to set this explicitly (fragile - but we do
already patch a few other things.)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1550188

Title:
  oslo_concurrency.lock_path: sensible default value is missing

Status in neutron package in Ubuntu:
  Triaged

Bug description:
  Prior to upstream switching to generation of configuration files,
  oslo_concurrency.lock_path was set explicitly in neutron.conf to
  $state_path/lock, providing a sane default for end users.

  With generation, this is not set explicitly in the configuration file
  and as a result is not set by default (it uses OSLO_LOCK_PATH by
  default which is unset in any package init/upstart/systemd configs).

  This causes problems when agents try to create locks to perform
  actions, and caused quite alot of problems in mitaka b2 for the
  openstack puppet modules team (as they mutate installed configuration
  files, rather than managing a complete file).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1550188/+subscriptions