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.
DescriptionMiroslav Hradílek
2020-06-25 08:05:01 UTC
Description of problem:
Commit
https://github.com/sosreport/sos/commit/745b4a236a0255ea76ffd273f3e2028ac46b4a89
introduced changes in journal collection and currently prevents collection of any journal unless '/var/log/journal/' exists.
I believe this is regression compared to previous versions of sosreport and at least some journal should be collected.
Version-Release number of selected component (if applicable):
sos-3.9-2.el7.noarch (unreleased)
How reproducible:
100%
Steps to Reproduce:
1. sosreport -o logs --batch -vvv
2. tar -tf resulting-sosreport.tar.xz
Actual results:
No journal is collected.
Expected results:
Some journal is collected.
Additional info:
Previously sosreport was collecting only full journal which may cause hang of sosreport collection on some systems.
Later it was incorrectly fixed to collect --since limited journal while it was still collecting whole journal as well (redundancy).
Now it is supposed to collect 3 journals (1 since limited, current boot, last boot). This is another redundancy when no '--since' is used. Because full journal (collected in such case) still contains current and last boot.
Opinion (what I'd consider cautious):
In case of non persistent journal:
* No since defined: collect whole journal.
* Since defined: collect --since limited journal.
In case of persistent journal:
* No since defined: collect only current and last boot.
* Since defined: collect --since limited journal.
--all-logs override: collect whole journal despite since and persistence.
The missing journal logs are one of very basic logfiles that sosreport collects and many support engineers rely on the file / cmd output. If nothing else, this must be collected in 7.9 GA. Hence bouncing priority/severity.
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 (sos bug fix and enhancement update), 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-2020:4068