← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1796976] [NEW] neutron.conf needs lock_path set for router to operate

 

You have been subscribed to a public bug:


This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:

- [X] This doc is inaccurate in this way: Using self-service network. Router fails to operate if lock_path is not set.
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output. 

Detail:
- Rocky clean install followinf the self-service network model
- While creating the sample networks and router the following issues arise when running throug the verifications
    1) ip netns <-- shows qdhcp namespaces but no qrouter
    2) openstack port list --router router <-- shows the interdaces in down states
After researching the log files i see in /var/log/neutron/neutron-l3-agent.log that the required parameter lock_path is missing

I've edited the /etc/neutron/neutron.conf and in the [oslo_concurrency] have set 
lock_path = /var/lib/neutron/tmp

After reinit:
- /var/log/neutron/neutron-l3-agent.log is clean, 
- ip netns shows 2 qdhcp and one qrouter as expected
- openstack port list --router router <- Ports are shown as active

Therefore my guess is that neutron install guide should be updated to
reflect this needed paramenter.

Thanks a lot in advance.

-----------------------------------
Release:  on 2018-10-08 10:46
SHA: 6084f10333d7662a4f98994db49fd52bf9bf68f2
Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/launch-instance-networks-selfservice.rst
URL: https://docs.openstack.org/install-guide/launch-instance-networks-selfservice.html

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: install-guide
-- 
neutron.conf needs lock_path set for router to operate
https://bugs.launchpad.net/bugs/1796976
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron.