[chassis] Fix fib & decap test #7660
Merged
Conversation
This file contains 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
added in PORTCHANNEL table anymore.
|
Add @arlakshm @wenyiz2021 for visibility. |
wenyiz2021
approved these changes
Mar 7, 2023
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
wangxin
pushed a commit
that referenced
this pull request
Mar 16, 2023
…ot (#7660) added in PORTCHANNEL table anymore.
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
sonic-net/sonic-buildimage#14028 removed the lag member collection from PORTCHANNEL table in config db. This breaks fib & decap tests. Fix this by retrieving lag members from PORTCHANNEL_MEMBER table.
This PR fixes #7658.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation