Skip to content

[action] [PR:16573] [Mellanox] Update spf test related to error status when sw control is enabled#19273

Closed
mssonicbld wants to merge 1 commit intosonic-net:202411from
mssonicbld:cherry/202411/16573
Closed

[action] [PR:16573] [Mellanox] Update spf test related to error status when sw control is enabled#19273
mssonicbld wants to merge 1 commit intosonic-net:202411from
mssonicbld:cherry/202411/16573

Conversation

@mssonicbld
Copy link
Collaborator

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:

  1. For active module, the expected state is OK
  2. For cmis passive module, when cmis ver is 3.0, the expected state is ModuleLowPwr, else it is OK
  3. For non cmis passive module, the expected state is 'Not supported'

When software control is disabled, the port error status keeps the original behaviour

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
  • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405
  • 202411

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:

  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'

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

… enabled (sonic-net#16573)

* Update spf platform test related to error status, due to sonic-net/sonic-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

* fix issue caused by the vs

* sfp test just run on physical setup

* update sfp tests

1. For cmis passive module, when cmis ver is 3.0, the expected state is ModuleLowPwr, else it is OK
@mssonicbld
Copy link
Collaborator Author

Original PR: #16573

@mssonicbld
Copy link
Collaborator Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kperumalbfn
Copy link
Collaborator

Closing this PR as this PR(#19264) has all the changes

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.

3 participants