-
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
zebra: Fix ip protocol route-map issue. #17474
base: master
Are you sure you want to change the base?
zebra: Fix ip protocol route-map issue. #17474
Conversation
Do we need a topotest to check such a foobar? |
I'm not sure matters a whole bunch for this case |
Yes, I am adding topotest also |
a036be1
to
d349867
Compare
@riw777 I have also added topotest . Can you please review my changes ? |
@ton31337 Added |
d349867
to
d0a47a3
Compare
@sougata-github-nvidia please fix frrbot and let's merge it. |
"ip/ipv6 protocol any route-map <route map>" cli is setting wrong route type ( ZEBRA_ROUTE_MAX ), It should set route type ZEBRA_ROUTE_ALL. Ticket: #4101560 Signed-off-by: Sougata Barik <[email protected]>
d0a47a3
to
86b2946
Compare
@ton31337 I have fixed the frrbot. |
"ip/ipv6 protocol any route-map " cli is setting wrong route type (ZEBRA_ROUTE_MAX), It should set route type ZEBRA_ROUTE_ALL.
After executing the above CLI, routes are not scheduled for processing with routemap.
Reason: CLI set route-type=ZEBRA_ROUTE_MAX but Zebra checks ZEBRA_ROUTE_ALL in rib_update_route_node().
FRR restart solves the issue, and filter works as expected, because restart route install flow is different and its checks are proper.
After this code change all the api's are in synced, and right FLAG is used.
CLI, rib_update_route_node() , zebra_route_map_check ()
Ticket: #4101560