fix the everflow ipv6 failure on dualtor A-A#10228
fix the everflow ipv6 failure on dualtor A-A#10228kevinskwang merged 6 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:
|
|
@kevinskwang pls assign one feature owner to help review this PR. |
|
Please add backport request to 202305 branch too |
|
observed below failure: |
|
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:
|
|
@XuChen-MSFT - The comment is addressed. Please help to review. |
|
/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:
|
|
Hi @kevinskwang , @XuChen-MSFT , the PR is approved. Could you help with the Azure.sonic-mgmt failures? Not certain if these are due to the code changes. Could you help with the merge? |
|
@yanjundeng pls fix the pr test failure |
|
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:
|
|
@kevinskwang resolved. Pls help review and merge. |
* fix the everflow ipv6 failure on dualtor A-A * change comment * add logging * add one line * remove spaces * remove white space
* fix the everflow ipv6 failure on dualtor A-A * change comment * add logging * add one line * remove spaces * remove white space
|
Cherry-pick PR to 202305: #12060 |
|
Cherry-pick PR to 202311: #12061 |
* fix the everflow ipv6 failure on dualtor A-A * change comment * add logging * add one line * remove spaces * remove white space
* fix the everflow ipv6 failure on dualtor A-A * change comment * add logging * add one line * remove spaces * remove white space
This reverts commit 21401f2.
…" (sonic-net#12161) This reverts commit 21401f2.
…" (sonic-net#12161) This reverts commit 21401f2.
… (#12167) This reverts commit 21401f2. Co-authored-by: bingwang-ms <[email protected]>
Description of PR
After debug and investigation, this failure of "test_everflow_ipv6" on dualtor A-A including two issues:
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 # (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 this fix on A-A, A-S and single T0.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation