-
Notifications
You must be signed in to change notification settings - Fork 720
Adds logic to get default disk and check disk type #3399
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
vvolam
reviewed
Jul 8, 2024
keboliu
reviewed
Jul 31, 2024
The syslogger-to-logger change is unrelated to the sonic-utilities change and breaks backwards compatibility. It should be a separate commit once SysLogger is in all the older versions.
Merged
8 tasks
@prgeor please help review/merge. Thanks. |
keboliu
reviewed
Sep 10, 2024
keboliu
approved these changes
Sep 10, 2024
prgeor
reviewed
Sep 23, 2024
prgeor
approved these changes
Oct 28, 2024
@bingwang-ms please help cherry-pick to 202405 branch, thanks! |
mssonicbld
pushed a commit
to mssonicbld/sonic-utilities
that referenced
this pull request
Nov 6, 2024
* Added function to check if disk is SATA * Fixed eval bug unconvered by UT * Changed logger to syslogger; fixed UT failures * Added checks for partitions and filtered_disks; fixed static analysis issues * Fix static analysis errors E303, E711 * Changed information delivery semantics per review comment * Reverted syslogger to logger to maintain backward compatibility The syslogger-to-logger change is unrelated to the sonic-utilities change and breaks backwards compatibility. It should be a separate commit once SysLogger is in all the older versions. * Changed Disk 'type' --> 'Type' for uniformity * Made the fields look uniform * Disk Type Support for eMMC devices * Removed old sonic_ssd import
Cherry-pick PR to 202405: #3601 |
mssonicbld
pushed a commit
that referenced
this pull request
Nov 6, 2024
* Added function to check if disk is SATA * Fixed eval bug unconvered by UT * Changed logger to syslogger; fixed UT failures * Added checks for partitions and filtered_disks; fixed static analysis issues * Fix static analysis errors E303, E711 * Changed information delivery semantics per review comment * Reverted syslogger to logger to maintain backward compatibility The syslogger-to-logger change is unrelated to the sonic-utilities change and breaks backwards compatibility. It should be a separate commit once SysLogger is in all the older versions. * Changed Disk 'type' --> 'Type' for uniformity * Made the fields look uniform * Disk Type Support for eMMC devices * Removed old sonic_ssd import
8 tasks
mssonicbld
added a commit
to mssonicbld/sonic-utilities.msft
that referenced
this pull request
Apr 15, 2025
…ash drive is plugged in Fix `show platform ssdhealth` not showing expected output when a usb flash drive is plugged in. <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md ** Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "closes #xxxx", "fixes #xxxx" or "resolves #xxxx" so that GitHub automatically closes the related issue when the PR is merged. If you are adding/modifying/removing any command or utility script, please also make sure to add/modify/remove any unit tests from the tests directory as appropriate. If you are modifying or removing an existing 'show', 'config' or 'sonic-clear' subcommand, or you are adding a new subcommand, please make sure you also update the Command Line Reference Guide (doc/Command-Reference.md) to reflect your changes. Please provide the following information: --> #### What I did When 'show platform ssdhealth' is not supplied with a device name and a usb flash drive is attached we show incorrect output as we deduce incorrect device name from 'lsblk' command and pass it to ssdutil. I removed this incorrect deduction of the device name. #### How I did it Instead of incorrectly deducing the device using the lsblk command we can instead not pass any device name as argument to the ssdutil and it will automatically choose the device on which /host partition is mounted which is the primary storage device in our case as per the PR: sonic-net/sonic-utilities#3399 #### How to verify it Run `sudo show platform ssdhealth` without any arguments with a flash drive plugged into the sonic switch. #### Previous command output (if the output of a command-line utility has changed) ``` root@qa-eth-vt19-1-4280:~# show platform ssdhealth Disk Type : NVME Device Model : N/A Health : N/A Temperature : N/A ``` #### New command output (if the output of a command-line utility has changed) ``` root@qa-eth-vt19-1-4280:/home/admin# show platform ssdhealth Disk Type : NVME Device Model : Virtium VTPM24CEXI080-BM110006 Health : 100.0% Temperature : 51.0C ``` In the case where the user passes the device name as argument to the command (`show platform ssdhealth /dev/nvme0n1`) output remains the same and no changes have been made.
mssonicbld
added a commit
to Azure/sonic-utilities.msft
that referenced
this pull request
Apr 15, 2025
…ash drive is plugged in (#166) Fix `show platform ssdhealth` not showing expected output when a usb flash drive is plugged in. <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "closes #xxxx", "fixes #xxxx" or "resolves #xxxx" so that GitHub automatically closes the related issue when the PR is merged. If you are adding/modifying/removing any command or utility script, please also make sure to add/modify/remove any unit tests from the tests directory as appropriate. If you are modifying or removing an existing 'show', 'config' or 'sonic-clear' subcommand, or you are adding a new subcommand, please make sure you also update the Command Line Reference Guide (doc/Command-Reference.md) to reflect your changes. Please provide the following information: --> #### What I did When 'show platform ssdhealth' is not supplied with a device name and a usb flash drive is attached we show incorrect output as we deduce incorrect device name from 'lsblk' command and pass it to ssdutil. I removed this incorrect deduction of the device name. #### How I did it Instead of incorrectly deducing the device using the lsblk command we can instead not pass any device name as argument to the ssdutil and it will automatically choose the device on which /host partition is mounted which is the primary storage device in our case as per the PR: sonic-net/sonic-utilities#3399 #### How to verify it Run `sudo show platform ssdhealth` without any arguments with a flash drive plugged into the sonic switch. #### Previous command output (if the output of a command-line utility has changed) ``` root@qa-eth-vt19-1-4280:~# show platform ssdhealth Disk Type : NVME Device Model : N/A Health : N/A Temperature : N/A ``` #### New command output (if the output of a command-line utility has changed) ``` root@qa-eth-vt19-1-4280:/home/admin# show platform ssdhealth Disk Type : NVME Device Model : Virtium VTPM24CEXI080-BM110006 Health : 100.0% Temperature : 51.0C ``` In the case where the user passes the device name as argument to the command (`show platform ssdhealth /dev/nvme0n1`) output remains the same and no changes have been made.
nmoray
pushed a commit
to nmoray/sonic-utilities
that referenced
this pull request
Jun 25, 2025
* Added function to check if disk is SATA * Fixed eval bug unconvered by UT * Changed logger to syslogger; fixed UT failures * Added checks for partitions and filtered_disks; fixed static analysis issues * Fix static analysis errors E303, E711 * Changed information delivery semantics per review comment * Reverted syslogger to logger to maintain backward compatibility The syslogger-to-logger change is unrelated to the sonic-utilities change and breaks backwards compatibility. It should be a separate commit once SysLogger is in all the older versions. * Changed Disk 'type' --> 'Type' for uniformity * Made the fields look uniform * Disk Type Support for eMMC devices * Removed old sonic_ssd import
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
Fix for sonic-buildimage issue 9407
To be merged
How I did it
Added logic using python libraries blkinfo and psutil to get the default disk, and the disk type (SATA/non-SATA).
How to verify it
call
sudo ssdutil
on a device with non-SATA disk (such as EUSB). Expected output is:Also ran a modified test_show_platform_ssdhealth (See sonic-mgmt PR mentioned above) on switches with all 4 disk types and verified that test was either skipped or passed. Logs attached: test_show_platform_ssdhealth.txt
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)