Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The lstopo plug-in has been added to the sos package. The plug-in captures machine topology/numa node information from hwloc packages, and thus allows users to understand which devices or memory are assigned to which node.
Created attachment 1127639[details]
lstopo-no-graphics > topo.txt
Could you please add
lstopo-no-graphics > topo.txt
(ASCII output)
and PNG output
lstopo topo.png (see the attached file)
to sosreport?
It provides nice information about CPU topology and PCI connectivity. It's very useful when debugging and tuning the performance of server - to allocate the jobs to the right NUMA node, to see to which NUMA node network card is connected and so on. At the moment there is no comparable report in sosreport.
Could you please add package "lstopo-no-graphics" to sos dependencies so that it's installed when sos is installed?
"lstopo-no-graphics" - unlike "lstopo" - does not depend on X.
Thanks a lot
Jirka
(In reply to Jiri Hladky from comment #7)
> Could you please add package "lstopo-no-graphics" to sos dependencies so
> that it's installed when sos is installed?
>
> "lstopo-no-graphics" - unlike "lstopo" - does not depend on X.
>
> Thanks a lot
> Jirka
sosreport - even with lstopo plugin contained - does not _depend_ on lstopo-no-graphics package. sos will simply detect if the package is present and only if so, it will run the commands in the plugin. Otherwise, sos can run without lstopo-no-graphics without an issue.
A request to add lstopo-no-graphics to sos dependencies is like a request to add there e.g. httpd (since mentioned in apache plugin).
> sosreport - even with lstopo plugin contained - does not _depend_ on
> lstopo-no-graphics package. sos will simply detect if the package is present
> and only if so, it will run the commands in the plugin. Otherwise, sos can
> run without lstopo-no-graphics without an issue.
>
> A request to add lstopo-no-graphics to sos dependencies is like a request to
> add there e.g. httpd (since mentioned in apache plugin).
OK, thanks for the explanation.
Pavel is correct - this is a policy decision. We only depend on packages that are required by the sos runtime (python libs mostly). Everything else is collected opportunistically - we run approx. 800 possible commands today and adding package dependencies for all of these would lead to an explosion in the dep list for sos and also for the basic installation (since sos is in a group that is included in most of these install types).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2380.html
Created attachment 1127639 [details] lstopo-no-graphics > topo.txt Could you please add lstopo-no-graphics > topo.txt (ASCII output) and PNG output lstopo topo.png (see the attached file) to sosreport? It provides nice information about CPU topology and PCI connectivity. It's very useful when debugging and tuning the performance of server - to allocate the jobs to the right NUMA node, to see to which NUMA node network card is connected and so on. At the moment there is no comparable report in sosreport.