-
Notifications
You must be signed in to change notification settings - Fork 746
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
Skip all admin down ports for non-Mellanox device #6433
Skip all admin down ports for non-Mellanox device #6433
Conversation
…om's device Signed-off-by: xuliping <[email protected]>
This pull request introduces 1 alert when merging c36013a into c41f842 - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging e8ee2b5 into 1620b7d - view on LGTM.com new alerts:
|
@@ -2481,15 +2481,8 @@ def _check_port_buffer_info_and_return(duthost, table, ids, port, expected_profi | |||
else: | |||
if is_mellanox_device(duthost): | |||
buffer_items_to_check = buffer_items_to_check_dict["down"][key_name] | |||
elif is_broadcom_device(duthost) and (asic_type in ['td2', 'td3'] or speed <= '10000'): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove is_broadcom_device
condition? We also have other platform such as marvell
, seems like this change will also cause skipping happening on other platforms, not just broadcom.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The special handling is needed only for mellanox. buffermgr will not attach any profiles for admin down ports on other platforms
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lipxu could you update your PR title to Skip all admin down ports for non-Mellanox device
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, @Blueve , have updated the title.
Updated the commit last time, but forgot to update the title, sorry for the confusion.
* remove asic type and speed check, skip all admin down ports on broadcom's device What is the motivation for this PR? There was no BUFFER_PROFILE_TABLE for admin down ports How did you do it? Skip all admin down ports for Broadcom device How did you verify/test it? Verify the original failure case Signed-off-by: xuliping <[email protected]>
* remove asic type and speed check, skip all admin down ports on broadcom's device What is the motivation for this PR? There was no BUFFER_PROFILE_TABLE for admin down ports How did you do it? Skip all admin down ports for Broadcom device How did you verify/test it? Verify the original failure case Signed-off-by: xuliping <[email protected]>
* remove asic type and speed check, skip all admin down ports on broadcom's device What is the motivation for this PR? There was no BUFFER_PROFILE_TABLE for admin down ports How did you do it? Skip all admin down ports for Broadcom device How did you verify/test it? Verify the original failure case Signed-off-by: xuliping <[email protected]>
* remove asic type and speed check, skip all admin down ports on broadcom's device What is the motivation for this PR? There was no BUFFER_PROFILE_TABLE for admin down ports How did you do it? Skip all admin down ports for Broadcom device How did you verify/test it? Verify the original failure case Signed-off-by: xuliping <[email protected]>
Signed-off-by: xuliping [email protected]
Description of PR
Summary:
Fixes # (issue)
Skip all admin down ports for Broadcom device
Type of change
Back port request
Approach
What is the motivation for this PR?
There was no BUFFER_PROFILE_TABLE for admin down ports
How did you do it?
Skip all admin down ports for Broadcom device
How did you verify/test it?
Verify the original failure case
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation