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.

What is the nature and description of the request?
currently the spacewalk-debug portion of the sosreport command is set to time out after 300 seconds. this poses an issue for satellite servers that have a large amount of data to generate with the spacewalk-debug. we would like to increase this timeout

Why does the customer need this? (List the business requirements here)
it would make supporting our customers that much easier (also, the customers are generally uneasy when they see the sosreport throw a timeout error)

How would the customer like to achieve this? (List the functional requirements here)
mmello++ has written an upstream patch for this enhancement: https://github.com/spacewalkproject/spacewalk/pull/532

For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
we have successfully reproduced the issues on internal servers, so we can test on the same when the patch is backported

List any affected packages or components.
sosreport, spacewalk-debug

Would the customer be able to assist in testing this functionality if implemented?
yes

my apologies, upstream patch is here:
https://github.com/sosreport/sos/pull/989/commits/c0a8aaca6ba01e8cfde8bc18ad30cf3849f6b2bf

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-2018:1920