fix the everflow testbed failure on dualtor A-A#11351
fix the everflow testbed failure on dualtor A-A#11351svelamal wants to merge 2 commits intosonic-net:masterfrom
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
Trailing whitespace is not introduced in this PR. Seems to have been there before too (#7748) |
lolyu
left a comment
There was a problem hiding this comment.
Please format your PR description.
Done |
XuChen-MSFT
left a comment
There was a problem hiding this comment.
LGTM, and pass local test
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@svelamal pls fix the pr test failure |
|
PR is obsolete, changes are included in #12022 |
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
Back port request
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