-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Revert "[Arista]: Fix TH5 egress pool creation failure with BCM YAML … #20245
Conversation
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! @Janetxxx , you might need to retry the test. I believe the kvm-test are not relavant to this PR.
@rick-arista as FYI . |
@kperumalbfn as FYI too. |
@rick-arista Please check the latest ingress/egress pool size. |
hi @Janetxxx , since we are hitting this conflict, we will have to manually cherry pick this change to 202405 once this PR is merged. |
@r12f I will do it once this PR gets merged. |
…file and SAI update on 07/16 (sonic-net#19640)" (sonic-net#20245) This reverts commit 0344d4a.
Cherry-pick PR to 202311: #20272 |
…file and SAI update on 07/16 (sonic-net#19640)" (sonic-net#20245) This reverts commit 0344d4a.
…file and SAI update on 07/16 (sonic-net#19640)" (sonic-net#20245) This reverts commit 0344d4a.
This reverts commit 0344d4a.
Why I did it
Because the issue arose from mixing 200G and 400G ports, but the deployment environment does not involve this mix, the issue will not occur, so this change is not necessary.
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
N/A
A picture of a cute animal (not mandatory but encouraged)