Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[action] [PR:11008] QoSHdrmPoolsize _tx_disable_enable for all destination ports in lag #12025

Merged
merged 1 commit into from
Mar 17, 2024

Conversation

mssonicbld
Copy link
Collaborator

Description of PR

Summary:
Since testQosHeadroomPoolsize test takes more than one source port as input, even after tx disable, the packets could still hash from the other ports. Hence tx_disable has to be applied on all ports in the destination lag to block all the traffic during tx_disable.
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205
  • 202305

Approach

Since testQosHeadroomPoolsize test takes more than one source port as input, even after tx disable, the packets could still hash from the other ports. Hence tx_disable has to be applied on all ports in the destination lag to block all the traffic during tx_disable.
This was achieved by
-Collecting all the dst_port_ids ports associated with the src_port_ids
-Sending all the dst_port_ids in a list, instead of sending a single dst_port_id in tx_disable

What is the motivation for this PR?

Intermitted failure of testQosHdrmPoolsize test

How did you do it?

Executed Qos test suite and verify the results

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

…onic-net#11008)

* QoSHdrmPoolsize_collecting dst ports in lag for tx_disable_enable
@mssonicbld
Copy link
Collaborator Author

Original PR: #11008

@mssonicbld mssonicbld merged commit 5e50c9e into sonic-net:202305 Mar 17, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants