Hi, I solved this issue using a interface without a IP at the physical_interface_mappings option in the /etc/neutron/plugins/ml2/linuxbridge_agent.ini compute's file. This interface must be configured with ifupdown in the /etc/network/interfaces, using the following code:

auto INTERFACE_NAME
iface INTERFACE_NAME inet manual
    up ip link set dev $IFACE up
    down ip link set dev $IFACE down

Hi shrapneel,

Could you clarify what you did to fix the problem?

In my case, I have the following new interfaces after openstack subnet create

tape8a7b19f-31@if2 and brqf217961a-f5.

The log references this tap device.. Error in agent loop. Devices info: {'current': {'tape8a7b19f-31'}, ...

I tried adding the two interfaces to the bridge with brctl addif brqf217961a-f5 tape8a7b19f-31 enp0s8, but I'm not really sure if that's the right move. enp0s8 is my provider network.

Thanks!

Had the same problem. Thought it's a bug of newest neutron. My problem was that interfaces, created after openstack subnet create weren't connected to my nic interface with the same error log. Solved it with brctl addif ... connect to linuxbridge port (must be repeated after reboot) I'm new in Linux and have no better solution

Hi, I solved this issue installing neutron 15.0.2 and apply an additional patch.

My environment is as below: OS: ubuntu 18.04.4 Openstack: train series

In my case, I can't install the neutron 15.0.2 from repository which is http://ubuntu-cloud.archive.canonical.com/ubuntu (http://ubuntu-cloud.archive.canonical...) bionic-updates/train. I guess it is not available currently.

So I installed neutron 15.0.2 by using pip3. Current neutron version is 15.0.2.

$ sudo pip3 install neutron

And then I have met another issue with TypeError.

I found new patch in the neutron repo. The patch is https://github.com/openstack/neutron/commit/7593f95a741aec62d9956175ce6d3ce1b1abb9a0#diff-4d838767dbc610e974ad2e1550a5ef89 (https://github.com/openstack/neutron/...)

I applied the above patch on correct location(/usr/local/lib/python3.6/dist-packages/neutron).

Finally, you can do this to all neutron members(controller and compute nodes).

I spent much time because I missed applying this solution to all compute nodes and new neutron source location.--;

I hope you can solve this issue. Thanks.

Hi,

What version of Neutron You are using? Is it the same version on neutron-server and neutron-linuxbridge-agent?