Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BFD stays for neighbor after overwriting with a config that doesn't have it #18357

Open
2 tasks done
oribon opened this issue Mar 10, 2025 · 1 comment
Open
2 tasks done
Labels
triage Needs further investigation

Comments

@oribon
Copy link

oribon commented Mar 10, 2025

Description

Spotted on frr-k8s ci. When applying a config that has BFD and then one that does not via the frr-reload.py script the neighbor still has bfd configured, e.g:

neighbor 10.x.x.x bfd

Version

bug happens on both 9.1.0, 9.1.3.
on 10.2.1 it works as expected

How to reproduce

first.conf.txt
second.conf.txt
(the ips are not sensitive - what we use in ci that deploys a kind cluster)
Always reproducible by appling first then second:

python3 /usr/lib/frr/frr-reload.py --reload --overwrite --stdout first.conf
python3 /usr/lib/frr/frr-reload.py --reload --overwrite --stdout second.conf

Expected behavior

the neighbor to have no BFD after applying a config that has no bfd.

Actual behavior

the neighbor still has bfd configured:

neighbor 10.x.x.x bfd

Additional context

I think this can be solved by bringing #15536 to 9.x
Thanks!

Checklist

  • I have searched the open issues for this bug.
  • I have not included sensitive information in this report.
@oribon oribon added the triage Needs further investigation label Mar 10, 2025
@Jafaral
Copy link
Member

Jafaral commented Mar 11, 2025

Why not upgrade to a newer version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

2 participants