Bug 2055547

Summary:	sos report does not honor plugin's default plugin_timeout
Product:	Red Hat Enterprise Linux 8	Reporter:	Pavel Moravec <pmoravec>
Component:	sos	Assignee:	Jan Jansky <jjansky>
Status:	CLOSED ERRATA	QA Contact:	Radek Duda <rduda>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	8.6	CC:	agk, bmr, mhradile, plambri, pmoravec, rduda, sbradley, theute
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.6	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sos-4.2-14.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2055548 (view as bug list)		Environment:
Last Closed:	2022-05-10 15:16:38 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:
Embargoed:
Bug Depends On:
Bug Blocks:	2055548

Description Pavel Moravec 2022-02-17 08:29:13 UTC

Description of problem:
Wired plugins' default_tieout is silently ignored. This means, default "sos report" will ignore foreman's default_timeout = 1800 and will use default --plugin-timeout default value 300. Which would often truncate the plugin's execution in the middle.

https://github.com/sosreport/sos/pull/2864 needs to be backported to 8.6/9.0


Version-Release number of selected component (if applicable):
sos-4.2-*


How reproducible:
100%


Steps to Reproduce:
1. sos report -o foreman --batch --build
2. In generated sosreport:

grep -A10 foreman -m2 ${sosdir}/sos_reports/manifest.json


Actual results:
2. shows:
..
--
                "foreman": {
                    ..
                    "timeout": 300, 
                    ..


Expected results:
2. must show:
..
--
                "foreman": {
                    ..
                    "timeout": 1800, 
                    ..

Additional info:

Comment 6 errata-xmlrpc 2022-05-10 15:16:38 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 (sos bug fix and enhancement update), 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://access.redhat.com/errata/RHEA-2022:1998