Ported the fix https://github.com/FRRouting/frr/pull/18601 from FRR community#22408
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
lipxu
left a comment
There was a problem hiding this comment.
Built and verified the internal 202411 image with the PR. No issues.
Verify case:
1: Run the previous test_frr.py script, 50 iterations, no issue found.
2: Repeat running the script bgp/test_traffic_shift.py for more than 100 iterations, no issue found.
3: Repeat loading config from minigraph with TSA for more than 300 iterations, no issue found.
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ea7d969 to
d60c5d8
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@yxieca @StormLiangMS @prsunny Can we merge this fix? |
|
Cherry-pick PR to 202505: #23021 |
…ity (#1675) Sync PR #22408 from sonic-net/sonic-buildimage to 202412. Original PR: sonic-net/sonic-buildimage#22408 Co-authored-by: sudhanshukumar22 <[email protected]>
…ity (#1675) Sync PR #22408 from sonic-net/sonic-buildimage to 202412. Original PR: sonic-net/sonic-buildimage#22408 Co-authored-by: sudhanshukumar22 <[email protected]>
Ported the fix FRRouting/frr#18601 from FRR community
Tested using static routes, save and reboot.
K>* 0.0.0.0/0 [0/0] via 10.59.128.1, eth0, 00:03:58
L * 1.1.1.1/32 is directly connected, Loopback0, 00:03:52
C>* 1.1.1.1/32 is directly connected, Loopback0, 00:03:52
C>* 10.59.128.0/20 is directly connected, eth0, 00:03:58
L> 10.59.142.159/32 is directly connected, eth0, 00:03:58
C>* 11.1.0.0/16 is directly connected, vsh0, 00:03:58
L> 11.1.22.238/32 is directly connected, vsh0, 00:03:58
C>* 20.1.1.0/24 is directly connected, Ethernet0, 00:02:22
L> 20.1.1.2/32 is directly connected, Ethernet0, 00:02:22
S>* 40.1.1.1/32 [1/0] is directly connected, Ethernet0, weight 1, 00:00:16
S>* 40.1.1.2/32 [1/0] is directly connected, Ethernet0, weight 1, 00:00:02
Tested branch (Please provide the tested image version)
FRR 10.0.1