oslo_concurrency.lock_path: sensible default value is missing
Bug #1550188 reported by
James Page
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
openstack-pkg-tools (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
python-oslo.concurrency (Ubuntu) |
Fix Released
|
High
|
Corey Bryant |
Bug Description
Prior to upstream switching to generation of configuration files, oslo_concurrenc
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/
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).
summary: |
- oslo_concurrency.lock_path default value is missing + oslo_concurrency.lock_path: sensible default value is missing |
Changed in neutron (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → ubuntu-16.02 |
Changed in python-oslo.concurrency (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in neutron (Ubuntu): | |
milestone: | ubuntu-16.02 → none |
To post a comment you must log in.
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.)