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

[Launchpad Bug Tracker]

This bug was fixed in the package python-oslo.concurrency -
3.0.0-1ubuntu1

---------------
python-oslo.concurrency (3.0.0-1ubuntu1) xenial; urgency=medium

  * d/p/lock-path-tempfile.patch: Cherry picked from upstream to set default
    of lock_file to a tempfile if OSLO_LOCK_PATH isn't set (LP: #1550188).
  * d/rules: Run tests for available Py3 versions instead of hardcoded Py3.4.

 -- Corey Bryant <corey.bryant at canonical.com>  Fri, 26 Feb 2016 08:21:02
-0500

** Changed in: python-oslo.concurrency (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  oslo_concurrency.lock_path: sensible default value is missing

Status in neutron package in Ubuntu:
  Won't Fix
Status in openstack-pkg-tools package in Ubuntu:
  Won't Fix
Status in python-oslo.concurrency package in Ubuntu:
  Fix Released

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