sonic-net / sonic-mgmt

Configuration management examples for SONiC
Other
200 stars 732 forks source link

[Bug][T2]: `qos/test_qos_sai.py::testQosSaiLossyQueue` fails with `dst_port_id does not have a sys port id configured` #15679

Closed arista-nwolfe closed 1 week ago

arista-nwolfe commented 1 week ago

Issue Description

Specifically the multi_dut variants like:

multi_dut_longlink_to_shortlink
multi_dut_shortlink_to_shortlink
multi_dut_shortlink_to_longlink

Fail on qos/test_qos_sai.py::testQosSaiLossyQueue with:

E           dst_port_id: 32, src_port_id: 2 src_port_vlan: None
E           actual dst_port_id: 33
E           FAIL
E
E           ======================================================================
E           FAIL: sai_qos_tests.LossyQueueTest
E           ----------------------------------------------------------------------
E           Traceback (most recent call last):
E             File "saitests/py3/sai_qos_tests.py", line 3995, in runTest
E               "dst_port_id does not have a sys port id configured"
E           AssertionError: dst_port_id does not have a sys port id configured
E
E           ----------------------------------------------------------------------
E           Ran 1 test in 22.550s
E
E           FAILED (failures=1)

Looking at the PTF command we can see the problem is that the dst_sys_ports={} (Pdb) p cmd '/root/env-python3/bin/ptf --test-dir saitests/py3 sai_qos_tests.LossyQueueTest --platform-dir ptftests --qlen=10000 --platform remote -t \'router_mac=\'"\'"\'2c:dd:e9:6c:c7:f1\'"\'"\';src_server=\'"\'"\'172.24.156.37:9092\'"\'"\';port_map_file=\'"\'"\'/root/ptf_test_port_map.json\'"\'"\';sonic_asic_type=\'"\'"\'broadcom\'"\'"\';sonic_version=\'"\'"\'branch.2024 05-ars.eb065b35-buildimage.origin.202405-nightly-dbg-2024.11.13.22.44\'"\'"\';src_dut_index=0;src_asic_index=0;dst_dut_index=1;dst_asic_index=0;dut_username=\'"\'"\'admin\'"\'"\';dut_password=\'"\'"\'password\'"\'"\';dst_server=\'"\'"\'172.24.156.38:9092\'"\'"\';platform_asic=\'"\'"\'broadcom-dnx\'"\'"\';test_port_ids={0: {0: [0, 2, 4, 6, 8, 10, 12, 13, 15, 16]} , 1: {0: [32, 34, 36, 38, 40, 42, 44, 45]}};dscp=8;ecn=1;pg=0;buffer_max_size=3220805000;headroom_size=\'"\'"\'0\'"\'"\';dst_port_id=32;dst_sys_ports={};dst_port_ip=\'"\'"\'10.0.0.65\'"\'"\';dst_port_2_id=36;dst_port_2_ip=\'"\'"\'10.0.0.73\'"\'"\';src_port_id=2;src_port_ip=\'"\'"\'10.0.0.5\'"\'"\';src_port_vlan=None;pkts_num_leak_out=5;pkts_num_trig_egr_drp=2179 900;hwsku=\'"\'"\'Arista-7800R3A-36DM2-C36\'"\'"\';pkts_num_margin=200\' --debug info --log-file /tmp/sai_qos_tests.LossyQueueTest.log --socket-recv-size 16384 --test-case-timeout 1850 --disable-ipv6 --disable-vxlan --disable-geneve --disable-erspan --disable-mpls --disable-nvgre'

Results you see

Argument dst_sys_ports={} is wrong when passed into PTF test: sai_qos_tests.LossyQueueTest specifically on the multi_dut variants.

Results you expected to see

dst_sys_ports shouldn't be an empty dictionary in sai_qos_tests.LossyQueueTest

Is it platform specific

generic

Relevant log output

No response

Output of show version

No response

Attach files (if any)

No response

arista-nwolfe commented 1 week ago

Closing issue, was something wrong with something we had internal