-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update sonic-frr submodule to FRR 8.2.2 #11502
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
Conversation
It should also be backported to 202205 |
Need merge this issue for 202205. |
I went through the list of patches that were removed in the FRR upgrade #10691. There is one patch of concern. src/sonic-frr/patch/0009-Link-local-scope-was-not-set-while-binding-socket-for-bgp-ipv6-link-local-neighbors.patch In FRR Reverted: sonic-net/sonic-frr@6740a19 (FRRouting/frr#8430) However, this patch was introduced in SONiC but never reverted. Now with upgrading to FRR and without this patch won’t we be facing issues? |
Please note that patch file 0009-Link-local-scope.. has been replaced with 0008-Link-local-scope..: Regarding the changes in the old 0009-Link-local-scope patch file, there were two changes originally. One of the changes (in bgp_update_address()) has been carried to the new patch file, and the other change (in bgp_zebra_nexthop_set()) is already present in the 8.2.2 code. I hope this clarifies. |
/easycla |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your explanation. However I see the changes in patch 0008-Link-local-scope-was-not-set-while-binding-socket-for-bgp-ipv6-link-local-neighbors.patch are not in upstream FRR since they were reverted. I am not sure if SONiC would allow patches that are not in upstream. @lguohan @prsunny @abdosi can you please provide feedback here?
@prsunny could you please help to review prev comment? As 202205 should include the new frr version I believe we need to push this with high prio. If fix still need to be done let's close the gap |
*The sonic-frr was upgraded to FRR 8.2.2 as part of PR sonic-net#10691. However, sonic-frr/frr submodule was still referring to previous 7.5 version. Update the sonic-frr/frr submodule to 8.2.2 commit id. Fixes issue sonic-net#11484.
*The sonic-frr was upgraded to FRR 8.2.2 as part of PR #10691. However, sonic-frr/frr submodule was still referring to previous 7.5 version. Update the sonic-frr/frr submodule to 8.2.2 commit id. Fixes issue #11484. Co-authored-by: Hasan Naqvi <[email protected]>
Why I did it
The sonic-frr was upgraded to FRR 8.2.2 as part of PR #10691. However, sonic-frr/frr submodule was still referring to previous 7.5 version. Update the sonic-frr/frr submodule to 8.2.2 commit id. Fixes issue #11484.
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Update sonic-frr/frr submodule to frr 8.2.2 commit 79188bf
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)