What were you trying to do that didn't work?

On OpenShift we have been configuring BGP routes in order to remove some static routes at node level, and we realized that when we removed the static routes of the nodes via NMState (which use NetworkManager under the hood), the FRR is not aware of these routes removal, then when we configure BGP to learn the prfixes matching with the removed routes, seems that FRR is not aware of the static routes removed and can not apply the learned prefixes, keeping the static routes. Hence, even the statir routes is removed at node level, and the BGP is configured successfully, the node routing table is not updated accordingly with the BGP, as we expected.

What is the impact of this issue to you?

This behavior require a manual intervention, in the case of OCP restarting the speaker where the FRR is running, in order to keep in sync with the node routing table. So in a production environment we should not expect to restart the FRR in order to keep these changes in sync.

Please provide the package NVR for which the bug is seen:

frr-8.5.3-4.el9.x86_64

How reproducible is this bug?:

Steps to reproduce

1. Create static routes on the host
2. Run frr
3. Remove the static route
4. Configure BGP to learn prefixes for the ip range of the removed route
5. Check the BGP logs, and see that the prefix can not be add to the routing table because exist a static route.

Expected results

We expected that once the static route has been removed, FRR will be aware of that change on the networking settings, and the new BGP prefix will be added as a dynamic route to the node.

Actual results

The learned prefix is not applying on the rougint table because a static route to that ip range already exist (which is not because it was deleted before)

cc: fpaoline@redhat.com fbaudin@redhat.com