Bug 1308998

Summary: [RFE] Add lstopo text output to sosreport
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Hladky <jhladky>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Miroslav HradĂ­lek <mhradile>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: agk, bmr, cww, emcnabb, gavin, hkrzesin, jhladky, mhradile, mpetlan, plambri, prarit, sbradley
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://github.com/sosreport/sos/issues/719
Whiteboard:
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.
Story Points: ---
Clone Of:
: 1381912 (view as bug list) Environment:
Last Closed: 2016-11-04 04:57:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1203710, 1298112, 1313485, 1381912    
Attachments:
Description Flags
lstopo-no-graphics > topo.txt
none
lstopo topo.png output none

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