Public bug reported: 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). ** Affects: neutron (Ubuntu) Importance: High Status: Triaged ** Summary changed: - oslo_concurrency.lock_path default value is missing + oslo_concurrency.lock_path: sensible default value is missing ** Changed in: neutron (Ubuntu) Status: New => Triaged ** Changed in: neutron (Ubuntu) Importance: Undecided => High ** Changed in: neutron (Ubuntu) Milestone: None => ubuntu-16.02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550188 Title: oslo_concurrency.lock_path: sensible default value is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1550188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs