[dualtor][test gap] Add testcases to cover the faulty ycable #14680
+1,486
−0
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 # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To fix test gap: #12311
Signed-off-by: Longxiang Lyu lolv@microsoft.com
How did you do it?
To simulate a faulty ycabled, a templated
y_cable_simulated.py
is used to replace the originalycable
driver.With the faulty
ycable
driver, two testcases are added:test_switchover_probe_unknown
to verify dualtor could toggle as expected evenycabled
returns mux probeunknown
.test_switchover_peer_link_down
to verify dualtor could toggle as expected evenycabled
returns peer linkdown
.How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation