-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Missing route map error during startup for existing route-map #17052
Comments
You can ignore it (nothing broken functionally). This is because the BGP config is applied first, and route maps - afterward. |
@ton31337 So this is a "good" error? Is there any documentation of "good" errors that are meant to be ignored? How is an incorrect error not functionally broken? |
It's not an error, it's a warning.
Because the sessions are established only after the configuration parsing is done. |
I do find it unfortunate that issues are closed as completed, with the "solution" being to ignore the problem. It doesn't exactly create much confidence in the project. |
@SRv6d are you able to test/verify this .rpm? From here: https://ci1.netdef.org/browse/FRR-PULLREQ3-5409/artifact/shared/RedHat-9-x86_64-RPMs/. |
watchfrr fails to start, I get the following: I installed frr-10.3_dev_20241010_git.7b18afb-01.el9.x86_64.rpm, frr-pythontools-10.3_dev_20241010_git.7b18afb-01.el9.x86_64.rpm as well as frr-contrib-10.3_dev_20241010_git.7b18afb-01.el9.x86_64.rpm. Am I missing some? |
What is the libyang version? |
libyang version 2.0.7-2.el9 |
You have to use 2.1.128 (this is the recommended/required version for newer releases). Please upgrade. |
This version is from frr-10.3_dev_20241010_git.7b18afb-01.el9.x86_64.rpm included in the RPM directory you sent. How do I install the correct version separately? |
libyang package is here for RHEL9: https://ci1.netdef.org/browse/LIBYANG-LIBYANG21-13/artifact/shared/RedHat-9-x86_64-Packages. |
That was it, no more error during startup, thank you. |
Can we close this? |
Yes, appreciate the fix. |
Description
When starting the FRRouting systemd service, errors are logged for missing route maps, even though they are configured and show up at runtime.
Version
How to reproduce
Start FRR installed on Rocky Linux 9.4 through the stable repos using systemd and the following configurations:
Expected behavior
No missing route map errors for configured route maps.
Actual behavior
This is logged:
While vtysh shows them as configured:
Additional context
Full startup log:
Checklist
The text was updated successfully, but these errors were encountered: