Add dynamic detection of SOS “numa” plugin name #3068
Conversation
SamirMulani
force-pushed
the
sos-utils-fix
branch
from
e3bf0e0 to
2605e82
Compare
|
Run Logs: |
ras/sosreport.py
Outdated
| match = re.match(r"^(\w+)\s+(.*)$", plugins.strip()) | ||
| if match: | ||
| matched_plugin = match.group(1) | ||
| break |
There was a problem hiding this comment.
should this break in second if loop?
I feel something not in proper index.
sacsant
left a comment
sacsant
left a comment
There was a problem hiding this comment.
Rewrite the commit message in a proper format, explaining what the problem is and how this change fixes the problem. Also merge the 2 commits into one. I assume the second commit was added to address review comments.
SamirMulani
force-pushed
the
sos-utils-fix
branch
from
f6002b3 to
30d3ddc
Compare
Previously, the code used a hard-coded SOS NUMA plugin name (numa1). However, some distributions do not provide the numa1 plugin and instead use numa. This commit adds logic to dynamically detect the supported NUMA plugin for the running distribution. With this change, the correct plugin name (numa1 or numa) is selected automatically at runtime, improving portability across distros. Signed-off-by: “Samir <“samir@linux.ibm.com”>
3 participants
Previously, the code used a hard-coded SOS NUMA plugin name (numa1). However, some distributions do not provide the numa1 plugin and instead use numa. This commit adds logic to dynamically detect the supported NUMA plugin for the running distribution. With this change, the correct plugin name (numa1 or numa) is selected automatically at runtime, improving portability across distros.