[dualtor][utilities] confirm neighbor entry exists before checking tunnel routes#8029
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame 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. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
…nnel routes (#8029) Description of PR Summary: Fixes # (issue) This PR is to improve dualtor_io test utilities. sign-off: Jing Zhang zhangjing@microsoft.com What is the motivation for this PR? Checking tunnel routes when neighbor entry is missing is meaningless. How did you do it? Fetch ip address from config db, then check the neighbor entry.
Description of PR
Summary:
Fixes # (issue)
This PR is to improve dualtor_io test utilities.
sign-off: Jing Zhang zhangjing@microsoft.com
Type of change
Back port request
Approach
What is the motivation for this PR?
Checking tunnel routes when neighbor entry is missing is meaningless.
How did you do it?
Fetch ip address from config db, then check the neighbor entry.
How did you verify/test it?
Ran test_normal_op tests on dualtor testbeds.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation