-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[chassis] route_check fails on LC due to timeout on frr routes #18773
Comments
The issue will be triaged further in the chassis meeting |
@stephenxs @stepanblyschak @liat-grozovik : can you please help with this. |
@judyjoseph @arlakshm @mlok-nokia @ysmanman for viz. Will apply for master image also. |
Feature 'Install before advt.' might be disable for 202405. |
@anamehra Could you please share a tech support when the issue occurs? What is the route scale on the system? |
The route_check eventually finished. I saw it took a couple of more mins. We have 50K routes. I will check on show tech. |
this is currently still an issue with 202405 |
@deepak-singhal0408 - I have attached logs for routeCheck issue. |
this feature is enabled back in Master. #19836 |
Tried 2 iterations with device having 32k v4+32k v6 routes.. Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName 10.0.0.1 4 65200 61249 14398 0 0 0 01:02:57 1 ARISTA01T3 Iteration1: <<<<<<<<<<<<<<<<< real 3m16.387s Iteration2: <<<<<<<<<<<<<<<<<<<<<<<<< real 3m18.249s |
python -m cProfile -s time route_check.py Ordered by: internal time ncalls tottime percall cumtime percall filename:lineno(function) |
With following optimizations, route_check time is reduced to 1m30sec.
|
Description
On chassis, after the introduction of frr route check in route_check.py (sonic-net/sonic-utilities#2762), route_check.py may take more than 2 mins to finish. The current timeout is 2 mins which causes route check to fail and affects monit output. This affects the sonic-mgmt pretest check. Other test cases relying on monit output may also be affected.
The issue was opened for 202305 earlier which was fixed by reverting the feature for frr route check: #17403
This needs to be fixed for master.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: