[SWSS] Cherry-pick PR #4614 from sonic-net into Azure 202511_azd branch#224
Open
weimingx wants to merge 1 commit into
Open
[SWSS] Cherry-pick PR #4614 from sonic-net into Azure 202511_azd branch#224weimingx wants to merge 1 commit into
weimingx wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR cherry-picks the changes from upstream SONiC PR sonic-net/sonic-swss#4614 into the Azure 202511_azd branch to keep the Azure fork aligned with upstream fixes/enhancements.
Details
Cherry-picked commit(s) from upstream PR #4614
Preserves original commit history using -x for traceability
Ensures consistency between sonic-net and Azure-maintained sonic-swss.msft
Validation
Build completed successfully (SWSS / full image, if applicable)
Basic functionality verified in test environment (update if you ran specific tests)
Notes / Risks
No functional modifications beyond upstream changes
Low risk as this is a direct cherry-pick
Any conflicts during cherry-pick were manually resolved and verified