[SWSS:portsorch] fix child_ports checking in addLagMember and removeLagMember for strip tag #3343
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.
What I did
Added child_ports check in addLagMember and removeLagMember for strip tag
Why I did it
portorch sets LAG member's strip tag when adding subport:
but if a new member is added later, in addLagMember function, it does not handle strip tag anymore. Cause the new added lag member has wrong tag mode.
How I verified it
without this fix, I observed that addLagMember happened after addSubPort, the strip tag was not set to the LAG members.
Build the image with the fix, confirmed that the strip tag is set correctly even the addLagMember called after assSubPort.
(will add a testcase for this before convert it to formal PR)
Details if related