Skip to content

[action] [PR:21455] [Mellanox] Update SN5640 SIMX sensors.conf file#534

Merged
r12f merged 1 commit intoAzure:202412from
mssonicbld:cherry/msft-202412/21455
Jan 23, 2025
Merged

[action] [PR:21455] [Mellanox] Update SN5640 SIMX sensors.conf file#534
r12f merged 1 commit intoAzure:202412from
mssonicbld:cherry/msft-202412/21455

Conversation

@mssonicbld
Copy link
Collaborator

Why I did it

To have the right sensors.conf file for SN5640 SIMX

How I did it

Updated sensors.conf file under SN5640-SIMX platform folder

How to verify it

run 'sensors' command on Mellanox SN5640 SIMX, and make sure no errors in output

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

<!--
     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 "fixes #xxxx", or
     "closes #xxxx" or "resolves #xxxx"

     Please provide the following information:
-->

#### Why I did it
To have the right sensors.conf file for SN5640 SIMX

#### How I did it
Updated sensors.conf file under SN5640-SIMX platform folder
#### How to verify it
run 'sensors' command on Mellanox SN5640 SIMX, and make sure no errors in output
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->

#### Which release branch to backport (provide reason below if selected)

<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->

- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211
- [ ] 202305

#### Tested branch (Please provide the tested image version)

<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->

- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->

#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->

<!--
 Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->

#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->

#### A picture of a cute animal (not mandatory but encouraged)
@mssonicbld
Copy link
Collaborator Author

Original PR: sonic-net/sonic-buildimage#21455

@mssonicbld
Copy link
Collaborator Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@r12f
Copy link

r12f commented Jan 23, 2025

Pipeline is broken and PR is validated in sonic-net side. Urgent PR and low risk to merge. Merging with bypassing checks.

@r12f r12f merged commit d4d6a3b into Azure:202412 Jan 23, 2025
5 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants