fix for qos failures for master branch due to backplane changes#19495
fix for qos failures for master branch due to backplane changes#19495yxieca merged 8 commits intosonic-net:masterfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@prabhataravind and @bhavani This latest PR is raised extension to previous PR #16465 |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@congh-nvidia @wen587 please review |
prabhataravind
left a comment
There was a problem hiding this comment.
We can't have hard-coded IPs in generic code.
tests/common/devices/sonic.py
Outdated
| show_ip_int_output = self.shell("show ip interface")["stdout"] | ||
| # Build set of Ethernet ports with 18.x.202.0/31 IPs to exclude | ||
| excluded_ports = set() | ||
| for line in show_ip_int_output.strip().splitlines(): |
There was a problem hiding this comment.
There is already a common method to parse the show output:
sonic-mgmt/tests/common/devices/sonic.py
Line 1679 in 20847a8
There was a problem hiding this comment.
@congh-nvidia
used show_and_parse API instead of custom parsing.
|
In general the DPU interfaces could affect some tests, not only the QOS test. For us we just don't add those interfaces to the ansible/files/sonic_lab_links.csv. And then there is no need to change the existing tests. |
tests/common/devices/sonic.py
Outdated
| excluded_ports = self.get_backplane_ports() | ||
| for k, v in list(ip_ifs.items()): | ||
| if ((k.startswith("Ethernet") and (not k.startswith("Ethernet-BP")) and not is_inband_port(k)) or | ||
| if ((k.startswith("Ethernet") and (k not in excluded_ports) and not is_inband_port(k)) or |
There was a problem hiding this comment.
What is the current naming for this Ehternet-BP port?
There was a problem hiding this comment.
@wen587
The current naming as follows
Ethernet224 18.0.202.0/31 up/up N/A N/A
Ethernet232 18.1.202.0/31 up/up N/A N/A
Ethernet240 18.2.202.0/31 up/up N/A N/A
Ethernet248 18.3.202.0/31 up/up N/A N/A
Ethernet256 18.4.202.0/31 up/up N/A N/A
Ethernet264 18.5.202.0/31 up/up N/A N/A
Ethernet272 18.6.202.0/31 up/up N/A N/A
Ethernet280 18.7.202.0/31 up/up N/A N/A
bpar9
left a comment
There was a problem hiding this comment.
@nnelluri-cisco lets close on common approach for all SS dependent scripts which can be adopted by everyone
@congh-nvidia The DPU interfaces show up like below when all the DPU modules are active on the system These ineterfaces are not show up when DPU are in dark mode. Can u please double check and let me know? |
sure @bhavani |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@prabhataravind and @congh-nvidia |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
98c7c5f to
2420f3e
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Saravanan <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Guy Shemesh <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Nishanth Sampath Kumar <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: selldinesh <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Guy Shemesh <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Guy Shemesh <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Venkata Gouri Rajesh Etla <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: YiFan Wang <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Priyansh Tratiya <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Yael Tzur <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
|
Cherry-pick PR to 202511: #22301 |
|
pinged this PR to @prsunny to label and move forward |
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Raghavendran Ramanathan <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Zhuohui Tan <[email protected]>
Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass. Signed-off-by: Abhishek <[email protected]>
…c-net#19495) Approach exclude new DPU interfaces Ethernet-224 to Ethernet-280 What is the motivation for this PR? The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch. How did you verify/test it? Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
Description of PR
This fix is to address the issue introduced by smartswicth interafces naming from Ethernet-BP0 / Ethernet-BP7
To Ethernet224 / Ethernet280
Summary: Excluded the DPU interafces Ethernet-224 to Ethernet-280 from the minigraph_facts to avoid qos failures
Fixes # (issue)
Type of change
Back port request
Approach
exclude new DPU interfaces Ethernet-224 to Ethernet-280
What is the motivation for this PR?
The new DPU interfaces Ethernet-224 to Ethernet-280 is breaking test_qos_sai.py regression in latest master branch.
How did you do it?
How did you verify/test it?
Ran complete test_qos_sai.py regression under sonic-mgmt. with new changes and all tests pass.
Any platform specific information?
Platform: x86_64-8102_28fh_dpu_o-r0
HwSKU: Cisco-8102-28FH-DPU-O
ASIC: cisco-8000
Supported testbed topology if it's a new test case?
topo_t1_28_lag
Documentation