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.
1. Proposed title of this feature request
[RFE] include sosreport command line options --all-logs and --log-size= in /etc/sos.conf
3. What is the nature and description of the request?
Currently sosreport only takes --all-logs and --log-size= as command line options but are not permanently configurable via /etc/sos.conf.
4. Why does the customer need this? (List the business requirements here)
When having a huge environment and lots of admins dealing with it it's likely, especially in an escalation situation that one forgets to add theses parameters and not all files are collected needed for initial analysis when huge log files are created (e.g RHEV env).
Further on with puppet, ansible or any other config management in place it would be simple to roll out a common /etc/sos.conf covering this in case it could be configured there.
5. How would the customer like to achieve this? (List the functional requirements here)
make the --all-logs and --log-size options from sosreport command line also configurable via /etc/sos.conf
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
add options to /etc/sos.conf and see if all files (--all-logs) and files up to a certain size (--log-size) are collected.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
could not find any
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEL7
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-3.2-35.el7_2.3.noarch
11. Would the customer be able to assist in testing this functionality if implemented?
sure
Adjacent bug found so far:
https://github.com/sosreport/sos/pull/1651
that one would limit usage of the config file significantly, needs backporting as well.
Working on the FailedQA cause.
How to negate an option: the same way how to do via cmdline, e.g.:
all-logs=off (or disable or disabled or false, case insensitive)
The trick is that general options are disabled by default so there is no way to test disabling them. But one can try adding to [tunables] section e.g.:
process.lsof=off
to turn off collecting lsof by process plugin. (this was verified by me to work well).
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