Neutron l3 agent keeps restarting (Ubuntu)

[Francois Michaut]

After following neutron install guide, when trying to create a floating IP, the request succeeded, but the floating IP never became reachable.

Looking at neutron-l3-agent status, I could see that it was restarting every 2 seconds, failing with an exception of 'file not found /etc/neutron/fwaas_driver.ini'.

As a temporary fix, I touched the file to create an empty one, and the service started without any errors and the floating IP started working.

My configuration is exactly the one provided in the install guide, I didn't change anything.

Maybe the documentation should contain a step to avoid this issue ?

- [ ] This doc is inaccurate in this way: ______
- [x] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on OFTC

-----------------------------------
Release: 19.1.1.dev10 on 2019-08-21 16:09:09
SHA: d202e323d7f03edc56add8e83aeb9cddbbbce895
Source: https://opendev.org/openstack/neutron/src/doc/source/install/controller-install-ubuntu.rst
URL: https://docs.openstack.org/neutron/xena/install/controller-install-ubuntu.html

[Brian Haley (brian-haley)]

I don't see any mention of fwaas_driver.ini in the tree, the last occurrence was removed in https://review.opendev.org/c/openstack/neutron/+/770787 about a year ago. Can you tell which file in your deployment has this setting? Maybe it's just an old file or on an older branch. Thanks!

[Francois Michaut (fmichaut)]

Sure. Looks like it comes from the init script :

grep -rn fwaas_driver /etc

/etc/init.d/neutron-l3-agent:24:DAEMON_ARGS="--config-file=/etc/neutron/l3_agent.ini --config-file=/etc/neutron/fwaas_driver.ini"

[Brian Haley (brian-haley)]

This looks like an issue with your distribution and not neutron itself as /etc/init.d/neutron-l3-agent would have been created by them.

[Brian Haley (brian-haley)]

I would take a look at https://bugs.launchpad.net/charm-neutron-api/+bug/1934129 - I'm no charms expert but there are a lot of changes there regarding fwaas and the l3-agent.

[Francois Michaut (fmichaut)]

I am using Ubuntu 20.04, and I installed neutron with (roughly) the following commands :

add-apt-repository cloud-archive:xena
apt update
apt install -y neutron-server neutron-plugin-ml2 neutron-linuxbridge-agent neutron-l3-agent neutron-dhcp-agent neutron-metadata-agent

As per the install guide for neutron (option2) : https://docs.openstack.org/neutron/xena/install/controller-install-option2-ubuntu.html.

I didn't use charms

[Brian Haley (brian-haley)]

This command:

> add-apt-repository cloud-archive:xena

is not in the neutron documentation. It's going to install a non-standard version of Openstack components on your system. Looking in the package repositories for focal, it defaults to 16.0.x binaries for neutron, which is Ussuri, not Xena. You might need to use Microstack for that, but again, I'm not an expert on Ubuntu installation.

It might be that the docs need an update to reference Microstack in the future, we would have to ping someone from Ubuntu for their input. But since the file causing problems is part of your distro it's not something the neutron team can fix, I would file a bug with Ubuntu so they can help you out with it.

References:

https://packages.ubuntu.com/focal/neutron-l3-agent
https://releases.openstack.org/ussuri/
https://ubuntu.com/openstack/tutorials

[Oleg Bondarev (obondarev)]

Marking "Invalid" for neutron based on Brian's last comment

[Francois Michaut (fmichaut)]

I opened a bug on cloudarchive launchpad : https://bugs.launchpad.net/cloud-archive/+bug/1958863
It is getting resolved, you can close this