Remove S2 port bcm configs for Arista-7060X6-64PE-B-O128#23100
Remove S2 port bcm configs for Arista-7060X6-64PE-B-O128#23100StormLiangMS merged 1 commit intosonic-net:masterfrom
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
hi @dayouliu1 do you mind to help update the PR title to be explicit on what is changed for? e.g. Update Arista-7060X6-64PE-B-O128 bcm configs to remove the 2 service ports. |
|
@dayouliu1 could you check the conflict? |
31ddb12 to
5995fce
Compare
|
Conflict resolved |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
hi @dayouliu1 , have you tested this change and see if no more SAI crash would happen? |
Yes |
|
hi @dayouliu1 would you mind to file separate PR for 202412 and 202505? There are conflicts. |
…B-O128 (#1320) Sync PR #23100 from sonic-net/sonic-buildimage to 202412. Original PR: sonic-net/sonic-buildimage#23100 Co-authored-by: Dayou Liu <113053330+dayouliu1@users.noreply.github.com>
I see Riff already has a 202412 pick. 202505 pick: #23268 |
yep! trying to get the build out soon, so I went ahead :D , hopefully nothing crazy! ;P |
|
Hi @r12f, Does this PR need to be added to msft-202503 or will it happen automatically? |
|
Could we also get this backported to msft-202503, thanks! |
) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md ** Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it sonic-net/sonic-buildimage#23100 Change was only partially applied in the 202412 code sync ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 201811 - [ ] 201911 - [ ] 202006 - [ ] 202012 - [ ] 202106 - [ ] 202111 - [ ] 202205 - [ ] 202211 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> #### A picture of a cute animal (not mandatory but encouraged)
Why I did it
Update Arista-7060X6-64PE-B-O128 bcm configs, remove unneeded S2 port configs
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)