[action] [PR:12022] fix the everflow testbed failure on dualtor A-A#12059
Merged
mssonicbld merged 1 commit intosonic-net:202311from Mar 20, 2024
Merged
[action] [PR:12022] fix the everflow testbed failure on dualtor A-A#12059mssonicbld merged 1 commit intosonic-net:202311from
mssonicbld merged 1 commit intosonic-net:202311from
Conversation
Collaborator
Author
|
Original PR: #12022 |
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
2 participants
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
After debug and investigation, this failure of "test_everflow_testbed" on dualtor A-A including two issues:
the mux status is standby on the selected DUT.
the test pkts are not sent to selected DUT, which has everflow rule config.
The rootcause of 1 is due to BGP shutdown. In the script, it tries to shutdown all BGP during setup, which makes T1 not reachable from the TOR. Then the DUT moves itself into standby mode. That's from the design of mux state machine.
The rootcause of 2 is similiar to the following issue:
#8158
We need fall back to active-standby mode to test this scenario for
active-active ports.
Summary:
Fixes # (issue)
Fixes # (#9983)
Type of change
Bug fix
[x ] Testbed and Framework(new/improvement)
Test case(new/improvement)
Back port request
201911
202012
[x ] 202205
[x ] 202305
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Verified on A-A
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation