[action] [PR:12506] Fix everflow tests for active-active dualtor.#12603
Merged
mssonicbld merged 1 commit intosonic-net:202311from Apr 26, 2024
Merged
[action] [PR:12506] Fix everflow tests for active-active dualtor.#12603mssonicbld merged 1 commit intosonic-net:202311from
mssonicbld merged 1 commit intosonic-net:202311from
Conversation
8 tasks
Collaborator
Author
|
Original PR: #12506 |
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
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 #97
Type of change
Back port request
Approach
What is the motivation for this PR?
everflow/test_everflow_ipv6.pyfails on active-active dualtoreverflow/test_everflow_testbed.pyfails on active-active dualtor.Following pull requests attempted to fix everflow tests -
everflow/test_everflow_ipv6.py: fix the everflow ipv6 failure on dualtor A-A #10228everflow/test_everflow_testbed.py: fix the everflow testbed failure on dualtor A-A #12022PR10228 was reverted because in the fix, BGP was't being shutdown and TTL was set to 1 only for dualtor case but it introduced a new regression.
PR12022 relied on PR120228 ( the fact that BGP would stll run for dualtor-aa ) and after the revert of former, the fix no longer works as both ToRs become standby and validation inside fixture
validate_active_active_dualtor_setupfails.How did you do it?
The proposed fix is to use the fixture
setup_standby_ports_on_rand_unselected_tor_unconditionallyintroduced in PR11921, so that these tests can run active-standby mode even if we shutdown BGP, ICMP responder, etcHow did you verify/test it?
Verified on Arista-7260 platform with dualtor-aa topology with 202305 image.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation