-
Notifications
You must be signed in to change notification settings - Fork 680
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
Add multi-asic support for dropconfig #3735
base: master
Are you sure you want to change the base?
Add multi-asic support for dropconfig #3735
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
1a8c9ea
to
4f38e99
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
1818a66
to
b5a9fcb
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
b5a9fcb
to
06444ac
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@arlakshm @wenyiz2021 for awareness |
A gentle nudge to review the PR @vmittal-msft @tjchadaga . Thank you! |
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.
Changes looks fine. Could you get chance to test ToR to make sure it doesn't break anything ?
Thanks for reviewing @vmittal-msft! Here are the snapshots from ToR device testing as requested: |
Thanks. Please go ahead and merge. |
Resolved conflict for 202405 cherry-pick: #3775 |
What I did
This script was missed during the initial efforts to add multi-asic support.
How I did it
This is in accordance to the issue sonic-net/sonic-buildimage#15148 which tracks the multi-asic support for scripts in sonic-utilities.
How to verify it
The changes were verified by:
Running all the unit tests in sonic-utilities
Verifying the changes manually on a single-asic linecards
Verifying the changes manually on a multi-asic linecards
Screenshots of the manual tests:
Previous command output (if the output of a command-line utility has changed)
Single asic command outputs remain untouched
New command output (if the output of a command-line utility has changed)
New multi asic command outputs will start with the prefix: `For namespace: "