[sensors_create_metadata.yml]: playbook to create sensors meta data f…#713
Closed
praveen-li wants to merge 1 commit intosonic-net:masterfrom
Closed
[sensors_create_metadata.yml]: playbook to create sensors meta data f…#713praveen-li wants to merge 1 commit intosonic-net:masterfrom
praveen-li wants to merge 1 commit intosonic-net:masterfrom
Conversation
…or given hwsku. [sensors_meta_data.py]: Ansible module to create sensors meta data. Signed-off-by: Praveen Chaudhary <[email protected]> This playbook and module generates a file with sensors meta data which can be used with sensors test suite. Without this module user has to go through tedious process for creating this Meta data manually. [Review Note]: As of now sensors_create_metadata.yml is placed in main ansible directory. Kindly suggest the best directory for it.
wangxin
pushed a commit
to wangxin/sonic-mgmt
that referenced
this pull request
Oct 27, 2025
…ic-net#713) <!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR <!-- - Please include a summary of the change and which issue is fixed. - Please also include relevant motivation and context. Where should reviewer start? background context? - List any dependencies that are required for this change. --> Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 ### Approach #### What is the motivation for this PR? Missing the watchdog configure in the watchdog.yml so that the case `platform_tests/test_sequential_restart.py` failed #### How did you do it? This pull request introduces support for the `x86_64-nvidia_sn5640-r0` platform in the watchdog API tests by adding relevant timeout settings. #### How did you verify/test it? Check in the sn5640 platform #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
Submodule src/sonic-swss 2529d79..15652b2: > [mirrororch]: Add retry logic when deleting referenced mirror session (sonic-net#1104) Submodule src/sonic-utilities 0cfa942..c049e54: > [neighbor_advertiser]: Add sleep in setting mirror session and ACL rules (sonic-net#714) > [warm/fast reboot] continue executing when killing docker failed (sonic-net#713) > [ecnconfig] Validate input WRED parameters (sonic-net#579) Signed-off-by: Ying Xie <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
Why I did it sonic-swss-common needs to support SWIG wrapper for go. Submodule update for sonic-swss-common Incorporates: d63130c [[CI]Install libyang from common-lib when build bullseye (sonic-net#710) bfe123e Add decorator for Yang default value. (sonic-net#713) 1d66080 Use SWIGPYTHON to improve SWIG for GO wrapper. (sonic-net#714) How I did it I have updated sonic-swss-common repo, this PR is used to update submodule. How to verify it Build image, and sonic-gnmi pipeline will verify SWIG wrapper.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
[sensors_create_metadata.yml]: playbook to create sensors meta data for given hwsku.
[sensors_meta_data.py]: Ansible module to create sensors meta data.
Signed-off-by: Praveen Chaudhary [email protected]
This playbook and module generates a file with sensors meta data which can be used with
sensors test suite. Without this module user has to go through tedious process for creating this Meta data manually.
[Review Note]: As of now sensors_create_metadata.yml is placed in main ansible directory.
Kindly suggest the best directory for it.
Description of PR
This playbook and module generates a file with sensors meta data which can be used with
sensors test suite. Without this module user has to go through tedious process for creating this Meta data manually.
Summary:
Fixes # (issue)
Type of change
Approach
How did you do it?
Added new playbook and new ansible module.
How did you verify/test it?
Verified for Seastone-DX010.
$ ANSIBLE_KEEP_REMOTE_FILES=1 ansible-playbook -i lab -l falco-test-dut02 sensors_create_metadata.yml -e "file=/tmp/praveen/sensorsMetaData.txt hwsku=Seastone-DX010"
$ cat /tmp/praveen/sensorsMetaData.txt
Seastone-DX010:
alarms:
fan:
- dps460-i2c-11-5b/fan1/fan1_alarm
- dps460-i2c-11-5b/fan1/fan1_fault
- emc2305-i2c-13-4d/fan1/fan2_fault
- emc2305-i2c-13-4d/fan1/fan2_alarm
- emc2305-i2c-13-4d/fan3/fan5_alarm
- emc2305-i2c-13-4d/fan3/fan5_fault
- emc2305-i2c-13-4d/fan2/fan4_alarm
- emc2305-i2c-13-4d/fan2/fan4_fault
- emc2305-i2c-13-4d/fan5/fan1_alarm
- emc2305-i2c-13-4d/fan5/fan1_fault
- emc2305-i2c-13-4d/fan4/fan3_fault
- emc2305-i2c-13-4d/fan4/fan3_alarm
- dps460-i2c-10-5a/fan1/fan1_alarm
- dps460-i2c-10-5a/fan1/fan1_fault
- emc2305-i2c-13-2e/fan1/fan2_fault
- emc2305-i2c-13-2e/fan1/fan2_alarm
- emc2305-i2c-13-2e/fan3/fan4_alarm
- emc2305-i2c-13-2e/fan3/fan4_fault
- emc2305-i2c-13-2e/fan2/fan1_alarm
- emc2305-i2c-13-2e/fan2/fan1_fault
- emc2305-i2c-13-2e/fan5/fan3_fault
- emc2305-i2c-13-2e/fan5/fan3_alarm
- emc2305-i2c-13-2e/fan4/fan5_alarm
- emc2305-i2c-13-2e/fan4/fan5_fault
temp:
- dps460-i2c-11-5b/Power Supply 2 temp sensor 2/temp2_crit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 2/temp2_max_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 2/temp2_min_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 2/temp2_lcrit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 3/temp3_lcrit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 3/temp3_crit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 3/temp3_max_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 3/temp3_min_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 1/temp1_crit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 1/temp1_lcrit_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 1/temp1_min_alarm
- dps460-i2c-11-5b/Power Supply 2 temp sensor 1/temp1_max_alarm
- coretemp-isa-0000/Core 3/temp5_crit_alarm
- coretemp-isa-0000/Core 2/temp4_crit_alarm
- coretemp-isa-0000/Core 1/temp3_crit_alarm
- coretemp-isa-0000/Core 0/temp2_crit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 1/temp1_crit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 1/temp1_lcrit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 1/temp1_min_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 1/temp1_max_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 3/temp3_lcrit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 3/temp3_crit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 3/temp3_max_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 3/temp3_min_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 2/temp2_crit_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 2/temp2_max_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 2/temp2_min_alarm
- dps460-i2c-10-5a/Power Supply 1 temp sensor 2/temp2_lcrit_alarm
power:
- dps460-i2c-11-5b/pin/power1_alarm
- dps460-i2c-11-5b/vin/in1_max_alarm
- dps460-i2c-11-5b/vin/in1_crit_alarm
- dps460-i2c-11-5b/vin/in1_min_alarm
- dps460-i2c-11-5b/vin/in1_lcrit_alarm
- dps460-i2c-11-5b/pout1/power2_max_alarm
- dps460-i2c-11-5b/pout1/power2_crit_alarm
- dps460-i2c-11-5b/pout1/power2_cap_alarm
- dps460-i2c-11-5b/vout1/in3_crit_alarm
- dps460-i2c-11-5b/vout1/in3_min_alarm
- dps460-i2c-11-5b/vout1/in3_lcrit_alarm
- dps460-i2c-11-5b/vout1/in3_max_alarm
- dps460-i2c-11-5b/iout1/curr2_lcrit_alarm
- dps460-i2c-11-5b/iout1/curr2_crit_alarm
- dps460-i2c-11-5b/iout1/curr2_max_alarm
- dps460-i2c-11-5b/iin/curr1_max_alarm
- dps460-i2c-11-5b/iin/curr1_crit_alarm
- dps460-i2c-10-5a/pin/power1_alarm
- dps460-i2c-10-5a/vin/in1_max_alarm
- dps460-i2c-10-5a/vin/in1_crit_alarm
- dps460-i2c-10-5a/vin/in1_min_alarm
- dps460-i2c-10-5a/vin/in1_lcrit_alarm
- dps460-i2c-10-5a/pout1/power2_max_alarm
- dps460-i2c-10-5a/pout1/power2_crit_alarm
- dps460-i2c-10-5a/pout1/power2_cap_alarm
- dps460-i2c-10-5a/vout1/in3_crit_alarm
- dps460-i2c-10-5a/vout1/in3_min_alarm
- dps460-i2c-10-5a/vout1/in3_lcrit_alarm
- dps460-i2c-10-5a/vout1/in3_max_alarm
- dps460-i2c-10-5a/iout1/curr2_lcrit_alarm
- dps460-i2c-10-5a/iout1/curr2_crit_alarm
- dps460-i2c-10-5a/iout1/curr2_max_alarm
- dps460-i2c-10-5a/iin/curr1_max_alarm
- dps460-i2c-10-5a/iin/curr1_crit_alarm
non-zero:
fan:
- dps460-i2c-11-5b/fan1/fan1_input
- emc2305-i2c-13-4d/fan1/fan2_input
- emc2305-i2c-13-4d/fan3/fan5_input
- emc2305-i2c-13-4d/fan2/fan4_input
- emc2305-i2c-13-4d/fan5/fan1_input
- emc2305-i2c-13-4d/fan4/fan3_input
- dps460-i2c-10-5a/fan1/fan1_input
............
............
- dps460-i2c-10-5a/iout1/curr2_max
- - dps460-i2c-10-5a/iin/curr1_input
- dps460-i2c-10-5a/iin/curr1_crit
- - dps460-i2c-10-5a/iin/curr1_input
- dps460-i2c-10-5a/iin/curr1_max
psu_skips:
others:
- dps460-i2c-11-5b/pout1/power2_cap
- emc2305-i2c-13-4d/fan1/fan2_div
- emc2305-i2c-13-4d/fan3/fan5_div
- emc2305-i2c-13-4d/fan2/fan4_div
- emc2305-i2c-13-4d/fan5/fan1_div
- emc2305-i2c-13-4d/fan4/fan3_div
- dps460-i2c-10-5a/pout1/power2_cap
- emc2305-i2c-13-2e/fan1/fan2_div
- emc2305-i2c-13-2e/fan3/fan4_div
- emc2305-i2c-13-2e/fan2/fan1_div
- emc2305-i2c-13-2e/fan5/fan3_div
- emc2305-i2c-13-2e/fan4/fan5_div
$
Any platform specific information?
No. This module is developed to create meta data for all platform.
Supported testbed topology if it's a new test case?
NA
Documentation
Let me know if it is needed, I can create one.