Bug 1368479
| Summary: | sosreport timeout does not allow for a full capture of foreman-debug output for Satellite 6 systems | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Craig Donnelly <cdonnell> |
| Component: | sos | Assignee: | Pavel Moravec <pmoravec> |
| Status: | CLOSED ERRATA | QA Contact: | Miroslav Hradílek <mhradile> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | agk, aperotti, bmr, cdonnell, daniele, gavin, isenfeld, juwu, mhradile, plambri, sbradley |
| Target Milestone: | rc | Keywords: | OtherQA |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://github.com/sosreport/sos/pull/888 | ||
| Whiteboard: | |||
| Fixed In Version: | sos-3.4-1.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:08:12 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: | 1353215 | ||
|
Description
Craig Donnelly
2016-08-19 14:06:52 UTC
How much time it takes to generate full f-d and full sosreport (that calls also f-d)? Does sosreport print it timeouted on some command? Can you attach some f-d and sosreport tarballs as example? FYI sosreport calls "foreman-debug -g" to skip collecting some generic information that sosreport collects by itself - that prevents collecting some info twice. Decided to fix the generic "foreman-debug run takes longer than 5minutes timeout of sosreport" just by increasing the timeout to 15 minutes. Upstream PR: https://github.com/sosreport/sos/pull/888 POSTED to upstream. See also: https://github.com/Katello/katello-packaging/pull/329 where we aim to significantly improve the lengthest call of foreman-debug: task export. For QE: in case deeper verification than "yes, the parameter is changed in code" is preferred from your side, I can help with either installing Satellite, mocking test, or preparing environment for a real test. (In reply to Pavel Moravec from comment #5) > For QE: > > in case deeper verification than "yes, the parameter is changed in code" is > preferred from your side, I can help with either installing Satellite, > mocking test, or preparing environment for a real test. Hello, would you be able to verify the fix on a candidate RPM for RHEL7.4 (once available)? Our QE would appreciate it. I can confirm the change in plugin source. If there is no positive feedback from the customer I will verify this SanityOnly.
# diff -u old/BUILD/sos-3.3/sos/plugins/foreman.py /usr/lib/python2.7/site-packages/sos/plugins/foreman.py
--- old/BUILD/sos-3.3/sos/plugins/foreman.py 2016-06-29 20:24:47.000000000 +0200
+++ /usr/lib/python2.7/site-packages/sos/plugins/foreman.py 2017-05-22 22:40:13.000000000 +0200
@@ -30,6 +30,6 @@
path = self.get_cmd_output_path(name="foreman-debug")
self.add_cmd_output("%s -g -q -a -d %s" % (cmd, path),
- chroot=self.tmp_in_sysroot())
+ chroot=self.tmp_in_sysroot(), timeout=900)
# vim: set et ts=4 sw=4 :
# rpm -qf /usr/lib/python2.7/site-packages/sos/plugins/foreman.py
sos-3.4-4.el7.noarch
Verifying Sanity Only (based just on code). See comment 12. 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/RHBA-2017:2203 |