-
Notifications
You must be signed in to change notification settings - Fork 770
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
[Mellanox] Update spf test related to error status when sw control is enabled #16573
base: master
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…nic-buildimage#20964 When software control is enabled, the port error status is as follows: 1. For active module, the expected state is OK 2. For cmis passive module, the expected state is ModuleLowPwr 3. For non cmis passive module, the expected state is 'Not supported' when software control is disabled, the port error status keep the original behaviour
b76445a
to
5ce252f
Compare
/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). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
@prgeor Could you help review? |
We saw the returned error description is
Can this change handle such case? |
1. For cmis passive module, when cmis ver is 3.0, the expected state is ModuleLowPwr, else it is OK
No. This case looks like a real issue, which has been fixed by sonic-net/sonic-platform-common#538 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-mgmt |
/AzurePipelines run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
@prgeor Can you please help review? |
Description of PR
Update spf platform test related to error status, due to PR: sonic-net/sonic-buildimage#20964
When software control is enabled, the port error status is as follows:
When software control is disabled, the port error status keeps the original behaviour
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Update spf test related to error status when sw control is enabled
How did you do it?
When sw control is enabled, check the error stats as the following logic:
How did you verify/test it?
Run test_get_error_description and test_check_sfputil_error_status when sw control is enabled
Any platform specific information?
Mellanox
Supported testbed topology if it's a new test case?
Documentation