[Bug 1550188] Re: oslo_concurrency.lock_path: sensible default value is missing
Mathew Hodson
mathew.hodson at gmail.com
Sun Apr 24 07:28:51 UTC 2016
** Changed in: neutron (Ubuntu)
Milestone: ubuntu-16.02 => None
--
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
More information about the Ubuntu-openstack-bugs
mailing list