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:
** Changed in: python-oslo.concurrency (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1550188
Title:
I've just uploaded python-oslo.concurrency 3.0.0-1ubuntu1 which cherry
picks the patch from upstream that uses tempfile.tempdir for lock_path
if OSLO_LOCK_PATH is not set.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Marking won't fix for anything other than oslo_concurrency.
** Changed in: openstack-pkg-tools (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: neutron (Ubuntu)
Status: Triaged => Won't Fix
** Also affects: python-oslo.concurrency (Ubuntu)
Importance: Undecided
See this bug in Oslo concurrency:
https://bugs.launchpad.net/oslo.concurrency/+bug/1549972
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1550188
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openstack-pkg-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
Linked bug 1549972
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1550188
Title:
oslo_concurrency.lock_path: sensible default value is missing
To manage notifications
Throwing a test build into:
https://launchpad.net/~james-page/+archive/ubuntu/xenial
for nova and neutron for this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
I'm favouring:
2) set OSLO_LOCK_PATH in agent configurations across the package.
as we can apply that quite generically across all pkgs with an update to
openstack-pkg-tools + some minor delta on project specific configs.
--
You received this bug notification because you are a member of Ubuntu
** Also affects: openstack-pkg-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-pkg-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1550188
Title:
The change in neutron-legacy was introduced as part of the switch to
using generated config files:
https://github.com/openstack-dev/devstack/commit/30d5fae3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
For reference, devstack sets a load of these explicitly:
lib/nova:iniset $NOVA_CONF oslo_concurrency lock_path "$NOVA_STATE_PATH"
lib/neutron-legacy:iniset $NEUTRON_CONF oslo_concurrency lock_path
$DATA_DIR/neutron/lock
lib/cinder:iniset $CINDER_CONF oslo_concurrency lock_path
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.)
--
13 matches
Mail list logo
