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

[Test Gap]: T2:TSA-TSB service consistency on multi-asic linecards #17128

Open
deepak-singhal0408 opened this issue Feb 24, 2025 · 1 comment
Assignees
Labels
Chassis Test Gap New or existing test cases that need to be added for chassis platforms Test gap test-gap

Comments

@deepak-singhal0408
Copy link
Contributor

Issue Type

Test Gap

Description

SONiC T2: TSA-TSB service consistency on multi-asic linecards

Issue Details

With the recent enhancements of TSA-TSB service, where it will be invoked individually by each namespace swss service, need a testcase to validate the consistency of TSA-TSB service.
i.e ensure that back to back restart of the tsa-tsb service doesnt end up in inconsistent state(one asic ns in TSA whereas other in tsb etc)

Impact or Proposed Behavior

In different timing scenarios, we always expect to have consistenct behavior. I.e, when the service is running, the whole linecard is in TSA state, and once the timer expires, the DUT goes back to TSB state.

Importance or Severity

High

Is it platform specific

generic

Relevant log output

Output of show version

Attach files (if any)

No response

@deepak-singhal0408 deepak-singhal0408 self-assigned this Feb 24, 2025
@deepak-singhal0408 deepak-singhal0408 added Test gap Chassis Test Gap New or existing test cases that need to be added for chassis platforms labels Feb 24, 2025
@deepak-singhal0408
Copy link
Contributor Author

relevant issue: sonic-net/sonic-buildimage#21816

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chassis Test Gap New or existing test cases that need to be added for chassis platforms Test gap test-gap
Projects
Status: No status
Development

No branches or pull requests

2 participants