-
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
Frr bookworm upgrade #18233
Frr bookworm upgrade #18233
Conversation
@StormLiangMS,@liushilongbuaa PR: #18233 is conflict with MS internal repo |
/azpw ms_conflict |
Might be blocked on #18150. |
/AzurePipelines run Azure.sonic-buildimage |
Commenter does not have sufficient privileges for PR 18233 in repo sonic-net/sonic-buildimage |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
@hasan-brcm Can you trigger a rerun of the PR checks? |
Apr 16 run failed due to libsnmp: make[2]: *** [debian/rules:43: clean] Error 25 |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Could you remove the if-check and TODO comment in |
@StormLiangMS,@liushilongbuaa PR: #18233 is conflict with MS internal repo |
Done. Thx! |
@hasan-brcm Looks like there are build failures in building FRR for Bookworm, can you resolve those? Also, were you able to successfully build FRR for Bookworm locally? |
Hi @hasan-brcm any update here? |
/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). |
still target 202405 release |
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.
LGTM
hi @hasan-brcm @saiarcot895 this change LGTM, but I got one question for the support of bookworm. For BRCM SDK, I remember the current version we planed for 202405 release (11?) supports only bullseye. So for 202405, there would be only one container stay in bullseye, it is the syncd. All other containers would go to bookworm. And for later release, start from 202411, the syncd and others would be landed on bookworm, is this correct? |
@StormLiangMS BRCM SDK will remain on bookworm until 202411, eg, platform/broadcom/docker-syncd-brcm |
/azpw ms_conflict |
/azpw ms_conflict -f |
/azpw ms_conflict |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw ms_conflict |
1 similar comment
/azpw ms_conflict |
/azpw ms_conflict |
1 similar comment
/azpw ms_conflict |
Co-authored-by: Kalimuthu Velappan <kalimuthu.velappan@broadcom.com>
Why I did it
Migrate FRR To bookworm.
Work item tracking
How I did it
Makefile and docker config changes to refer to bookworm instead of bullseye.
How to verify it
Build bookworm frr docker.
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Migrate FRR to bookworm.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)