[201911][Arista] make fancontrol config more resilient on 7060CX-32S #17809
Conversation
This file contains 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
prgeor
approved these changes
Jan 18, 2024
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
There's only one new change related |
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.
Why I did it
In some rare cases the fancontrol config is invalid for DCS-7060CX-32S
There is no determinism in the kernel allocation of i2c bus number nor hwmon ids
If a driver takes too long to initialize another driver might initialize first thus leading sysfs path changes
Work item tracking
How I did it
Updated the fancontrol configuration to use some wildcards where determinism might be a problem.
How to verify it
Run fancontrol with this new configuration
Description for the changelog
Make fancontrol config more resilient on DCS-7060CX-32S