-
Notifications
You must be signed in to change notification settings - Fork 778
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
[test_genric_hash.py]: cisco platform checks fix #16135
[test_genric_hash.py]: cisco platform checks fix #16135
Conversation
/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). |
/azp run |
Commenter does not have sufficient privileges for PR 16135 in repo sonic-net/sonic-mgmt |
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.
@harjotsinghpawra can you add rest of the info in the PR description template - Motivation for PR (what the current checks were lacking) (2) also how/which topo it was verified and need verification for both lag & non-lag
@bpar9 Added more details in the PR |
logging.info('Check only one port in a portchannel received traffic') | ||
assert False, 'The traffic is balanced over portchannel members.' | ||
if hit_port_number == len(self.expected_port_groups[0]): | ||
logging.info('Check if all ports in a portchannel received traffic') |
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.
I think this change doesn't make sense here.The purpose of this function is to just check the load balancing not happening on the port channel.
assert _calculate_balance(expected_hit_cnt_per_port), "The balancing result is beyond the range." | ||
|
||
expected_total_hit_cnt = self.balancing_test_times * len(self.expected_port_list) | ||
lag_expected_total_hit_cnt = self.balancing_test_times * len(self.expected_port_groups[0]) |
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.
all the packet should reach to the same ECMP path in this function, the expected hit cunt should use expected_total_hit_cnt, rather than lag_expected_total_hit_cnt
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@kevinskwang Hi kevin , i think i miss understood the test cases . I though that normal ECMP and lag hashes are tested individually . But i understand in one case we don't have any ECMP hash algorithm enabled and only enable lag hash algo then we test lag hash. Vice versa is also true where ECMP hash is tested and lag hash is disabled . I have reverted my changes back and only kept platform checks specific to CISCO . I hope my understanding of case is now correct |
@harjotsinghpawra , can you modify the title and description of the PR reflecting the reduced changes which the PR now has. Should specify that you are making only cisco related platform checks and remove the check_balance fix info as you have dropped those changes. Approved the PR for the current Cisco related changes |
* [test_genric_hash.py]: cisco platform checks and some check_balance fix * line spaces and artifact fixes * indent fix * check_balance fixes revert commit
Cherry-pick PR to 202405: #16496 |
* [test_genric_hash.py]: cisco platform checks and some check_balance fix * line spaces and artifact fixes * indent fix * check_balance fixes revert commit
Cherry-pick PR to 202411: #16497 |
* [test_genric_hash.py]: cisco platform checks and some check_balance fix * line spaces and artifact fixes * indent fix * check_balance fixes revert commit
* [test_genric_hash.py]: cisco platform checks and some check_balance fix * line spaces and artifact fixes * indent fix * check_balance fixes revert commit
Description of PR
Cisco support different HASH algorithms and fields as of now than default
Some issues were because CISCO was not supporting certain hash algorithms and Fields which led to issues like below
some algorithm config is missing i have listed one of many errors whose root cause is same
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Tested it on T1/T0 cisco platforms where correct calulation was done after my fox and only supported fields were picked
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation