-
Notifications
You must be signed in to change notification settings - Fork 817
[Test Gap]: T2:TSA-TSB service consistency on multi-asic linecards #17128
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
Labels
Chassis Test Gap
New or existing test cases that need to be added for chassis platforms
Test gap
test-gap
Comments
relevant issue: sonic-net/sonic-buildimage#21816 |
11 tasks
arlakshm
pushed a commit
that referenced
this issue
Mar 28, 2025
What is the motivation for this PR? Issue details in #17128 Wrote a testcase to catch such issue in future How did you do it? Restart the startup_tsa_tsb service multiple times with varying intervals and validate its behavior at each step. How did you verify/test it? Execute the new testcase on a multi-asic linecard setup
amulyan7
pushed a commit
to amulyan7/sonic-mgmt
that referenced
this issue
Mar 31, 2025
What is the motivation for this PR? Issue details in sonic-net#17128 Wrote a testcase to catch such issue in future How did you do it? Restart the startup_tsa_tsb service multiple times with varying intervals and validate its behavior at each step. How did you verify/test it? Execute the new testcase on a multi-asic linecard setup
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this issue
Mar 31, 2025
What is the motivation for this PR? Issue details in sonic-net#17128 Wrote a testcase to catch such issue in future How did you do it? Restart the startup_tsa_tsb service multiple times with varying intervals and validate its behavior at each step. How did you verify/test it? Execute the new testcase on a multi-asic linecard setup
OriTrabelsi
pushed a commit
to OriTrabelsi/sonic-mgmt
that referenced
this issue
Apr 1, 2025
What is the motivation for this PR? Issue details in sonic-net#17128 Wrote a testcase to catch such issue in future How did you do it? Restart the startup_tsa_tsb service multiple times with varying intervals and validate its behavior at each step. How did you verify/test it? Execute the new testcase on a multi-asic linecard setup
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
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
The text was updated successfully, but these errors were encountered: