Skip to content

bgpd: fix premature deletion of already-stale routes during GR clearing (backport)#20804

Merged
donaldsharp merged 1 commit intoFRRouting:stable/10.5from
opensourcerouting:fix/backport_968ccc4713d192d0941c7e09d03128d00f21c669_10.5
Feb 13, 2026
Merged

bgpd: fix premature deletion of already-stale routes during GR clearing (backport)#20804
donaldsharp merged 1 commit intoFRRouting:stable/10.5from
opensourcerouting:fix/backport_968ccc4713d192d0941c7e09d03128d00f21c669_10.5

Conversation

@ton31337
Copy link
Member

No description provided.

When a peer goes down with GR enabled, routes already marked
BGP_PATH_STALE were incorrectly deleted instead of being preserved
for the current GR cycle. Remove the BGP_PATH_STALE check from both
bgp_clear_route_node() and clearing_clear_one_pi() so that stale
routes are re-marked rather than removed. Stale route cleanup remains
handled by bgp_clear_stale_route() on timer expiry.

Ticket: RM#4866286

Signed-off-by: Mitesh Kanjariya <mkanjariya@nvidia.com>
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@greptile-apps
Copy link

greptile-apps bot commented Feb 13, 2026

Target branch is not in the allowed branches list.

@donaldsharp donaldsharp merged commit 41861fb into FRRouting:stable/10.5 Feb 13, 2026
18 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants