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.

Bug 1482278

Summary:	crm_report no longer collects anything for sosreport
Product:	Red Hat Enterprise Linux 7	Reporter:	Ken Gaillot <kgaillot>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.4	CC:	abeekhof, aherr, cfeist, cluster-maint, djansa, jruemker, michele, mnovacek, rscarazz, sbradley, tbarron
Target Milestone:	rc	Keywords:	ZStream
Target Release:	7.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pacemaker-1.1.18-1.el7	Doc Type:	No Doc Update
Doc Text:	Prior to this update, the crm_report utility terminated with a fatal error if the user disabled searching for logs using the --sos-mode option without specifying any log files. Consequently, the sosreport tool was unable to collect any cluster log file. With this update, crm_report now correctly collects non-log information if no logs are found or specified, and the described problem no longer occurs.	Story Points:	---
Clone Of:
Clones:	1482852 (view as bug list)		Environment:
Last Closed:	2018-04-10 15:30:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1482852

Description Ken Gaillot 2017-08-17 00:11:56 UTC

Description of problem: Since commit 582e886d, pacemaker's crm_report no longer collects any information when --sos-mode is used (which is how sosreport calls it). The goal of the commit was to stop collecting logs that sosreport would already collect separately, but it triggers a fatal error, so nothing is collected.


Steps to Reproduce:
1. Configure a cluster and run it for a few minutes.
2. Run 'crm_report --sos-mode --from HH:MM:SS --to HH:MM:SS' replacing HH:MM:SS with the desired start and end times.

Actual results: Resulting tar file has nothing of interest in it.


Expected results: Resulting tar file contains configuration information, policy engine input files, etc.

Comment 2 Ken Gaillot 2017-08-17 17:25:42 UTC

Fixed upstream as of commit 6a387a3

Comment 5 michal novacek 2017-12-04 14:07:35 UTC

I have verified that crm_report creates correct sos-mode reports with
pacemaker-1.1.18-6.el7

---

> crm_mon --version
Pacemaker 1.1.18-6.el7
Written by Andrew Beekhof

> crm_report --sos-mode --from 14:00:00 --to 14:30:00
virt-265:   Collecting data from virt-265.cluster-qe.lab.eng.brq.redhat.com (12/04/2017 02:00:00 PM to 12/04/2017 02:30:00 PM)
virt-265:   Searching for where Pacemaker daemons live... this may take a while
virt-265:   Pacemaker daemons found in: /usr/libexec/pacemaker
virt-265:   Pacemaker config files found in: /var/lib/pacemaker/cib
virt-265:   Pacemaker policy engine inputs found in: /var/lib/pacemaker/pengine
virt-265:   Systemd journal will be only log collected
virt-265:   No log files found or specified with --logfile /some/path
virt-265:    
virt-265:   Collected results are available in /root/pcmk-Mon-04-Dec-2017.tar.bz2
virt-265:    
virt-265:   Please create a bug entry at
virt-265:       https://bugzilla.redhat.com/
virt-265:   Include a description of your problem and attach this tarball
virt-265:    
virt-265:   Thank you for taking time to create this report.
virt-265:    

> tar -C /tmp -xjvf /root/pcmk-Mon-04-Dec-2017.tar.bz2
pcmk-Mon-04-Dec-2017/
pcmk-Mon-04-Dec-2017/.env
pcmk-Mon-04-Dec-2017/collector
pcmk-Mon-04-Dec-2017/virt-265.cluster-qe.lab.eng.brq.redhat.com/
pcmk-Mon-04-Dec-2017/virt-265.cluster-qe.lab.eng.brq.redhat.com/sysinfo.txt
...
pcmk-Mon-04-Dec-2017/analysis.txt
pcmk-Mon-04-Dec-2017/report.summary

> ls -ltR /tmp/pcmk-Mon-04-Dec-2017/
/tmp/pcmk-Mon-04-Dec-2017/:
total 60
-rw-r--r--. 1 root root   279 Dec  4 14:50 analysis.txt
-rw-r--r--. 1 root root    14 Dec  4 14:50 report.summary
drwxr-xr-x. 3 root root  4096 Dec  4 14:50 virt-265.cluster-qe.lab.eng.brq.redhat.com
-rw-r--r--. 1 root root 45500 Dec  4 14:49 collector

/tmp/pcmk-Mon-04-Dec-2017/virt-265.cluster-qe.lab.eng.brq.redhat.com:
total 2332
-rw-r--r--. 1 root root      69 Dec  4 14:50 analysis.txt
-rw-r--r--. 1 root root    8763 Dec  4 14:50 journal.log
-rw-r--r--. 1 root root    2637 Dec  4 14:49 cib.txt
-rw-r--r--. 1 root root 2203402 Dec  4 14:49 corosync-blackbox-live.txt
...

Comment 8 errata-xmlrpc 2018-04-10 15:30:29 UTC

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:0860