Bug 1697813

Summary: Plugin timeouts must be higher than command timeouts within the plugin
Product: Red Hat Enterprise Linux 7 Reporter: Pavel Moravec <pmoravec>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: Miroslav Hradílek <mhradile>
Severity: high Docs Contact:
Priority: high    
Version: 7.7CC: agk, bmr, gavin, mhradile, ovasik, plambri, sbradley
Target Milestone: rc   
Target Release: 7.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sos-3.7-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1719885 (view as bug list) Environment:
Last Closed: 2019-08-06 13:15:47 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: 1719885    

Description Pavel Moravec 2019-04-09 07:21:53 UTC 
Description of problem:
There are few plugins (foreman, also satellite) where collect commands with timeout higher than default plugin timeout. That means the command timeout value ineffective.

This is a big problem for foreman plugin where few commands can take much longer (and also overall plugin runtime can be bigger than default 5minutes, in scaled environments). So these plugins must have default plugin timeout updated accordingly to the timeouts of their commands.


Version-Release number of selected component (if applicable):
sos 3.7-2


How reproducible:
100%


Steps to Reproduce:
1. Have a bigger Satellite6 (or mock the lengthy commands "su postgres -c .." by some "sleep 120")
2. run sosreport
3. Do the same on Sat5 on RHEL7 (if applicable at all, not sure if spacewalk packages for RHEL7 exist)


Actual results:
2. plugin timeouts


Expected results:
2. plugin should not timeout by default


Additional info:
Comment 4 errata-xmlrpc 2019-08-06 13:15:47 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://access.redhat.com/errata/RHEA-2019:2295