-
Notifications
You must be signed in to change notification settings - Fork 664
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
[202012] [generate_dump] allow to extend dump with plugin scripts #1945
Conversation
Signed-off-by: Stepan Blyshchak <[email protected]>
Signed-off-by: Stepan Blyshchak <[email protected]>
…ties into 202012-techsupport
@qiluo-msft could you please help to review? |
@qiluo-msft |
@noaOrMlnx With this PR merged, there are the following errors:
Check kvm t0 and kvm t1-lag for details. |
@stephenxs please retrigger and update, thanks! |
44ec4c8b [202012] [generate_dump] allow to extend dump with plugin scripts (sonic-net/sonic-utilities#1945) Signed-off-by: Stephen Sun <[email protected]>
A draft PR has been created for dry run: sonic-net/sonic-buildimage#9617 |
…ipts (sonic-net#1945)" This reverts commit 44ec4c8.
Update submodule sonic-utilities that contains the following commits: Revert "[202012] [generate_dump] allow to extend dump with plugin scripts (sonic-net#1945)" (sonic-net#1993) [soft-reboot] Add support for platforms based on Device Tree (sonic-net#1963) [Reclaiming buffer][202012] Database migrator for reclaiming buffer (sonic-net#1898) [202012] [generate_dump] allow to extend dump with plugin scripts (sonic-net#1945) Signed-off-by: dprital <[email protected]>
Signed-off-by: Noa Or [email protected]
What I did
Added support for tech support extension scripts,
by cherry-picking of #1335 to branch 202012
The purpose is to have dumps of extensions in SONiC techsupport, even without App Extension infrastructure.
The new application will write a file that contains the dump command into /usr/bin/debug-dump folder, and it will appear in the output of
show techsupport
command.How I did it
It looks at /usr/bin/debug-dump for scripts, if it finds one it will execute them and save the output to dump/ folder.
How to verify it
Write a simple scripts that outputs something and place it under /usr/bin/debug-dump/
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)