Dynamic routing: peer not removed from agent

Bug #1750129 reported by Dr. Jens Harbott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

Bug Description

After going through https://docs.openstack.org/neutron-dynamic-routing/latest/contributor/testing.html even after removing both the speaker from the agent and the peer from the speaker, the agent still continues trying to connect to the peer address.

Expected result would be seeing the connection attempts stop.

Tags: l3-bgp
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

I traced this back to an issue in ryu, see https://sourceforge.net/p/ryu/mailman/message/36260483/ .
This issue only happens when the agent is not able to establish a BGP session to the peer. When the BGP session is connected while the speaker is being removed, https://bugs.launchpad.net/bugs/1750383 is triggered instead.

A workaround might be to explicitly remove all peers (in the ryu driver) before shutting down the speaker, but I'd be fine with waiting for this to be fixed in ryu, too.

tags: added: l3-bgp
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.