Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionSteffen Froemer
2018-01-29 15:36:46 UTC
1. Proposed title of this feature request
Improve runtime for sosreport by adding the usage of threads to archiving method
3. What is the nature and description of the request?
The time for creating sosreport on systems with high amount of logs resulting in large archives, can be tuned by adding thread-support easily.
4. Why does the customer need this? (List the business requirements here)
On debugging issues in RHV environment, the sosreport will require to archive a lot of logs which in sum have a large amount of size. Archiving these items will need a lot of time, because sos is only using single-thread for creating the archive
5. How would the customer like to achieve this? (List the functional requirements here)
Using more processors for the archiving process
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Collect a sosreport without the tuning enabled and measure the time. With tuning enabled, the creation of sosreport would require less time.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
https://github.com/sosreport/sos/issues/1196
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap
9. Is the sales team involved in this request and do they have any additional input?
no
10. List any affected packages or components.
sos
11. Would the customer be able to assist in testing this functionality if implemented?
yes
This relies on sos upstream:
https://github.com/sosreport/sos/pull/1199
that depends on python-futures package, that is not in RHEL repo/channels.
Cond nack until the package is there (request for that in process).
(In reply to Pavel Moravec from comment #5)
> This relies on sos upstream:
>
> https://github.com/sosreport/sos/pull/1199
>
> that depends on python-futures package, that is not in RHEL repo/channels.
>
> Cond nack until the package is there (request for that in process).
There is already BZ for that, 1545357 , so devel_ack+ for 7.6.
(how one can remove devel cond nak? I can only change the type but can't reset it to None)
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-2018:3144