Fix drop_packets/test_configurable_drop_counters.py for active-active dualtor. #12500
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
vivekverma-arista
changed the title
|
hi @lolyu @theasianpianist could you help to take a look? |
lolyu
approved these changes
Apr 19, 2024
theasianpianist
approved these changes
Apr 23, 2024
StormLiangMS
approved these changes
Apr 26, 2024
|
hi @vivekverma-arista could you confirm if tested with 202305/202311 image? |
|
This has been tested with 202305 and 202311 image @StormLiangMS |
|
hi @vivekverma-arista could you confirm the result with T0 / T1 topo for this change? |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
May 16, 2024
Testcases fail in drop_packets/test_configurable_drop_counters.py fail in dualtor-aa because some of the traffic goes to the unselected ToR. How did you do it? Similar approach is taken as in sonic-net#11921 How did you verify/test it? Verified on Arista 7260 and Arista 7050 with both dualtor and dualtor-aa topology.
|
Cherry-pick PR to 202311: #12865 |
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
May 16, 2024
Testcases fail in drop_packets/test_configurable_drop_counters.py fail in dualtor-aa because some of the traffic goes to the unselected ToR. How did you do it? Similar approach is taken as in sonic-net#11921 How did you verify/test it? Verified on Arista 7260 and Arista 7050 with both dualtor and dualtor-aa topology.
8 tasks
|
Cherry-pick PR to 202305: #12866 |
8 tasks
mssonicbld
pushed a commit
that referenced
this pull request
May 16, 2024
Testcases fail in drop_packets/test_configurable_drop_counters.py fail in dualtor-aa because some of the traffic goes to the unselected ToR. How did you do it? Similar approach is taken as in #11921 How did you verify/test it? Verified on Arista 7260 and Arista 7050 with both dualtor and dualtor-aa topology.
mssonicbld
pushed a commit
that referenced
this pull request
May 16, 2024
Testcases fail in drop_packets/test_configurable_drop_counters.py fail in dualtor-aa because some of the traffic goes to the unselected ToR. How did you do it? Similar approach is taken as in #11921 How did you verify/test it? Verified on Arista 7260 and Arista 7050 with both dualtor and dualtor-aa topology.
mssonicbld
added
Included in 202305 branch
and removed
Created PR to 202305 branch
labels
mssonicbld
added
Included in 202311 branch
and removed
Created PR to 202311 branch
labels
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:
Fixes #
Type of change
Back port request
Approach
What is the motivation for this PR?
Testcases fail in
drop_packets/test_configurable_drop_counters.pyfail indualtor-aabecause some of the traffic goes to the unselected ToR.How did you do it?
Similar approach is taken as in #11921
How did you verify/test it?
Verified on Arista 7260 and Arista 7050 with both dualtor and dualtor-aa topology.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation