Fix test_neighbor_mac on t1-lag and t1-64-lag#13314
Fix test_neighbor_mac on t1-lag and t1-64-lag#13314bingwang-ms merged 4 commits intosonic-net:masterfrom
Conversation
tests/arp/test_neighbor_mac.py
Outdated
There was a problem hiding this comment.
better to add a wait_until logic here to wait and check.
|
@byu343 conflicts need to resolve. |
f364049 to
17062f4
Compare
|
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:
|
35d0086 to
d811bec
Compare
|
Please re-run the PR test. |
d811bec to
4a444eb
Compare
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 13314 in repo sonic-net/sonic-mgmt |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 13314 in repo sonic-net/sonic-mgmt |
|
Have triggered to rerun the failed jobs. |
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@byu343 code conflict. |
4a444eb to
a96e16f
Compare
Code conflict has been fixed |
A recent change sets this test to t1-only: sonic-net#12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
a96e16f to
1bb3018
Compare
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1bb3018 to
96f18cd
Compare
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: sonic-net#12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: sonic-net#12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
|
Cherry-pick PR to 202311: #13607 |
|
Cherry-pick PR to 202405: #13608 |
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: #12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: #12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: sonic-net#12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
|
Cherry-pick PR to 202305: #13879 |
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: #12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
* Fix test_neighbor_mac on t1-lag and t1-64-lag A recent change sets this test to t1-only: sonic-net#12952 The test can pass on topo t1 without any change. For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it. The fix here is to delete the intf from the portchanenl before testing it.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
A recent change applies this test to the topo of t1 and t1-variants:
#12952
The test can pass on topo t1 without any change.
For t1-lag or t1-64-lag, the Ethernet0 to test is in portchannel, so IP address cannot be set to it.
How did you do it?
The fix here is to remove the intf from the portchanenl before testing it.
Skip the test if Ethernet0 is not available or down at the beginning of test
Assert Ethernet0 is in routed state after removing it from portchannel
How did you verify/test it?
Run the test on t1-lag and t1-64-lag topo.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation