Ask Your Question
2

neutron.plugins.ml2.drivers.agent._common_agent KeyError: 'gateway'

asked 2019-12-09 02:58:26 -0600

ehsan gravatar image

Hi Everyone , I installed train on Ubuntu 18.0.4 Server . I've a problem with neutron . when I run openstack create subnet , my subnet created , but when I check neutron-linuxbridge-agent.log , it return this error

ERROR neutron.plugins.ml2.drivers.agent._common_agent KeyError: 'gateway' . ERROR neutron.plugins.ml2.drivers.agent._common_agent File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py", line 402, in _update_interface_ip_details

edit retag flag offensive close merge delete
add a comment

4 answers

Sort by ยป oldest newest most voted
0

answered 2020-01-01 20:27:19 -0600

mr-stack gravatar image

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!

edit flag offensive delete link more

Comments

Hi! I only added "brq..." into the bridge, as it is linuxbridge's interface and all "tap..." interfaces are created for subnets/instances (not rememver clearly)

My linux distributive was not intended to run OpenStack out of the box

shrapneel gravatar imageshrapneel ( 2020-01-23 02:59:00 -0600 )edit

Also i had problem that after reboot interfaces appeared with some delay - so i turned off ssh service for about 100 seconds wia rc.local script in order not to harm the system

shrapneel gravatar imageshrapneel ( 2020-01-23 03:03:39 -0600 )edit
add a comment
0

answered 2019-12-11 03:30:09 -0600

shrapneel gravatar image

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

edit flag offensive delete link more

Comments

It could be my distributive's package problem because later on i tried to install train on Ubuntu - and there were no any problems

shrapneel gravatar imageshrapneel ( 2020-01-23 03:05:48 -0600 )edit
add a comment
0

answered 2020-01-12 16:30:32 -0600

lcnzg gravatar image

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
edit flag offensive delete link more
add a comment
0

answered 2019-12-10 02:22:39 -0600

slaweq gravatar image

Hi,

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

edit flag offensive delete link more
add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

subscribe to rss feed

Stats

Asked: 2019-12-09 02:58:26 -0600

Seen: 256 times

Last updated: Dec 10 '19

Related questions

VM multicast corosync invalid packet data

Cannot Ping VMs

Neutron: Command not found

Openstack Neutron Instances not getting IP addresses

Domain admin can access entities out of scope

(Newton) SNAT drop default traffic

neutron-openvswitch-agent not starting up on compute node

Exact firewall rules for metadata agent on controller node

Neutron tenant networks

Instance HTTP issues