[GCU] Refresh DUT env before cacl test to avoid ip rule impact #16826
+3
−0
Conversation
This file contains 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
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
ADO: 31219916
Summary: Reload DUT before cacl test to avoid ip rule change by other tests
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
The initial ip rule was impact by other test. Since this is not config related change, so general DUT recover will not be executed on such DUT. The missing ip rule would cause comparison diff between initial and after test.
How did you do it?
Refresh ip table after reload DUT
How did you verify/test it?
E2E
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation