[Cherry-pick] [26777] [acl]: Exclude PortChannel members from LT2 ACL bindings - #1345
Merged
Merged
Conversation
Summary: Prevent LT2 ACL table creation from binding physical interfaces that are already members of PortChannels. Signed-off-by: Deeksha Rao <deerao@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> (cherry picked from commit 23dd5670957614e10f0165f1d29439e75ba6ed10)
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
bingwang-ms
approved these changes
Aug 5, 2026
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
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.
Description of PR
Summary:
Backport sonic-net/sonic-mgmt#26777 to the internal 202512 branch. Prevent LT2 ACL table creation from binding physical interfaces that are already members of PortChannels.
Fixes sonic-net/sonic-mgmt#26777
Type of change
Back port request
Approach
What is the motivation for this PR?
LT2 ACL setup can include physical interfaces that are already PortChannel members, causing invalid duplicate ACL bindings.
How did you do it?
Collected PortChannel members by namespace and excluded those interfaces when adding standalone upstream RIFs to the ACL table.
How did you verify/test it?
Resolved the 202512 cherry-pick conflict by retaining only the intended LT2 change. Verified the resulting diff and Python syntax.
Any platform specific information?
Applies to LT2 topologies.
Supported testbed topology if it's a new test case?
N/A; this is a fix to an existing ACL test.
Documentation
N/A.