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.
Bug 1308998 - [RFE] Add lstopo text output to sosreport
Summary: [RFE] Add lstopo text output to sosreport
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
URL: https://github.com/sosreport/sos/issu...
Whiteboard:
: 1294658 (view as bug list)
Depends On:
Blocks: 1203710 1298112 1313485 1381912
TreeView+ depends on / blocked
 
Reported: 2016-02-16 17:05 UTC by Jiri Hladky
Modified: 2016-11-04 04:57 UTC (History)
12 users (show)

Fixed In Version: sos-3.3-0.el7
Doc Type: Enhancement
Doc Text:
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.
Clone Of:
: 1381912 (view as bug list)
Environment:
Last Closed: 2016-11-04 04:57:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
lstopo-no-graphics > topo.txt (6.96 KB, text/plain)
2016-02-16 17:05 UTC, Jiri Hladky 		no flags Details
lstopo topo.png output (50.36 KB, image/png)
2016-02-16 17:06 UTC, Jiri Hladky 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2380 0 normal SHIPPED_LIVE sos bug fix and enhancement update 2016-11-03 13:52:35 UTC

Description Jiri Hladky 2016-02-16 17:05:44 UTC 
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.
Comment 1 Jiri Hladky 2016-02-16 17:06:22 UTC 
Created attachment 1127640 [details]
lstopo topo.png output
Comment 3 Pavel Moravec 2016-02-17 17:46:01 UTC 
*** Bug 1294658 has been marked as a duplicate of this bug. ***
Comment 4 Pavel Moravec 2016-02-20 15:52:23 UTC 
See upstream PR https://github.com/sosreport/sos/pull/771 - please comment there if having some concern.
Comment 5 Pavel Moravec 2016-03-07 17:34:04 UTC 
QE is on edge of their capacity for sos in 7.3 - would you be able to verify the plugin once available in sos package?
Comment 6 Jiri Hladky 2016-03-07 21:40:52 UTC 
Sure. I have changed the QA contact to myself.
Comment 7 Jiri Hladky 2016-03-10 13:50:38 UTC 
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
Comment 8 Pavel Moravec 2016-03-11 07:15:07 UTC 
(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).
Comment 9 Jiri Hladky 2016-03-11 09:24:27 UTC 
> 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.
Comment 10 Bryn M. Reeves 2016-03-11 13:08:54 UTC 
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).
Comment 11 Jiri Hladky 2016-03-11 13:26:00 UTC 
Yes, it makes sense.
Comment 16 errata-xmlrpc 2016-11-04 04:57:45 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.