Conversation
Downlink ports don't have BGP neighbors in case of T0, hence the above change is causing the key error. The proposed fix is to modify the testPorts dictionary with peer_addr_ipv6 only if it is defined.
|
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:
|
|
Hi @vmittal-msft @bingwang-ms, can you review this PR? |
b7d0672 to
9291e3f
Compare
|
Hi, @vmittal-msft can we backport this to 202311 as well, as the issue exists in that branch as well. #10941, the PR that introduced regression has backport requests to 202205, 202311 and 202305 out of which only 202311 PR has merged till now. |
|
@vivekverma-arista PR conflicts with 202311 branch |
|
@vivekverma-arista Can you file another PR for 202311 branch to resolve the conflict? |
|
Created PR: #12481 for 202311 |
|
@vivekverma-arista The issue is not completely fixed. I still see similar error. Can you please help fix? |
What is the motivation for this PR? The new test is a poorly written IPV6 variant of testQosSaiDscpQueueMapping. It is expected to fail across all platforms/topolgies because qos/test_qos_sai.py cannot support IPV6 variant of any of it's testcase because IPV6 is disabled on the DUT by qos_sai_base.py: https://github.com/sonic-net/sonic-mgmt/blob/master/tests/qos/qos_sai_base.py#L1811-L1826 Also the changes made for this test touch class scoped fixtures which causes all the other testcases to error out as well. How did you do it? Revert #10941 as well as the following fixes that were made to get around the issue Fix qos/test_qos_sai.py #12334 Skip IPV6 variant of testQosSaiDscpQueueMapping if IPV6 is not config… #12834 How did you verify/test it? Verfied on T0, T1 and T0-dualTor, #126 was not seen.
Description of PR
Summary: Fix qos/test_qos_sai.py
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Regression introduced by #12088
qos/test_qos_sai.pyfails with the following traceback -How did you do it?
Downlink ports don't have BGP neighbors in case of T0, hence the above change is causing the key error.
The proposed fix is to modify the testPorts dictionary with peer_addr_ipv6 only if it is defined.
How did you verify/test it?
Verified on Arista-7260 with dualtor topology.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation