[zebra]fix the assert issue when the nexthop type of ip route entry is blackhole. #5940
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- Why I did it
When adding the route entry which nexthop type is blackhole, the process of zebra crashed
- How I did it
admin@sonic:
$ vtysh$ show logging | grep zebraHello, this is FRRouting (version 7.2.1-sonic).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
sonic# configure
sonic(config)# ip route 10.0.0.0/8 blackhole
sonic(config)# admin@sonic:
Nov 16 09:03:24.160321 sonic INFO bgp#supervisord: zebra zebra: zebra/zebra_fpm.c:993: zfpm_build_route_updates: Assertion `data_len' failed.
Nov 16 09:03:26.851960 sonic INFO bgp#supervisor-proc-exit-listener: Process zebra exited unxepectedly. Terminating supervisor...
- How to verify it
- Which release branch to backport (provide reason below if selected)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)