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.
Bug 1271975 - sosreport collects "journalctl --list-boots" but the option is not available
Summary: sosreport collects "journalctl --list-boots" but the option is not available
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.2
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-15 08:17 UTC by masanari iida
Modified: 2015-10-15 10:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-15 10:13:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description masanari iida 2015-10-15 08:17:20 UTC 
Description of problem:
sosreport collects journalctl --list-boots,
but the result in sos_commands/systemd/journalctl_--list-boots
always "journalctl: unrecognized option '--list-boots'"

Version-Release number of selected component (if applicable):
sos-3.2-15.el7_1.8.noarch
systemd-208-20.el7_1.6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run sosreport
2. Extraxt xz file
3. See sos_commands/systemd/journalctl_--list-boots

Actual results:
journalctl: unrecognized option '--list-boots'

Expected results:
Boot time and date should be display.

Additional info:
It seemed journalctl in systemd-208-20.el7_1.6 doesn't have this option.
Either remove this command from sos, or backport this option into 
systemd-208-20.el7 is a solution.

Business impact : none
Comment 2 Bryn M. Reeves 2015-10-15 10:13:16 UTC 
This is not a bug in sos: we support multiple distributions from the same sos version meaning that there is some variation in the environment and tool capabilities where sos runs.

The same command on a recent Fedora system would produce something like:

$ cat sos_commands/systemd/journalctl_--list-boots
-3 cd6f638cafa4451bbff8f71f8e018388 Tue 2015-10-06 21:16:56 BST—Tue 2015-10-06 22:09:40 BST
-2 37aa3ac637d2499c9911566a14deb976 Tue 2015-10-06 22:09:50 BST—Wed 2015-10-07 10:15:56 BST
-1 c15e6ac9f12944069e6ace081d31201d Wed 2015-10-07 10:45:48 BST—Fri 2015-10-09 18:07:36 BST
 0 9180c1bf81f3466f93b9e656750098c6 Fri 2015-10-09 18:08:19 BST—Thu 2015-10-15 11:03:59 BST

> It seemed journalctl in systemd-208-20.el7_1.6 doesn't have this option.
> Either remove this command from sos, or backport this option into 
> systemd-208-20.el7 is a solution.

I believe persistent journald logs are disabled by policy in RHEL7 and that this is a requirement for any operation working with boot IDs, e.g.:

# journalctl -k -b -1
Failed to look up boot -1: Cannot assign requested address

Note that other products such as Atomic do use the journal (and this version of sos): if there is to be a change here it needs to be in the systemd packaging.
Note You need to log in before you can comment on or make changes to this bug.