Bug 989292

Summary:	SOS integration for pacemaker
Product:	Red Hat Enterprise Linux 6	Reporter:	Andrew Beekhof <abeekhof>
Component:	sos	Assignee:	Bryn M. Reeves <bmr>
Status:	CLOSED ERRATA	QA Contact:	Filip Holec <fholec>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.4	CC:	agk, bmr, dkutalek, fdinitto, fholec, gavin, psplicha
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sos-2.2-42.el6	Doc Type:	Enhancement
Doc Text:	Feature: Sos now supports collecting unified cluster diagnostic data via the crm_report tool. Reason: The crm_report command provides a simple mechanism to obtain cluster-wide configuration and diagnostic data. Result (if any):	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 22:41:44 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:	987355, 1002857

Description Andrew Beekhof 2013-07-29 02:49:43 UTC

Description of problem:

sosreport needs to take advantage of crm_report for cluster bugs if pacemaker is installed

As per IRC conversations, we probably want to run in single-node mode (by default crm_report obtains logs and support files for all cluster nodes).

       -S, --single-node
              single node operation; don't try to start report collectors on other nodes

You'll also want to specify where the output goes to with:

       --dest a custom destination directory/file

Other arguments that can be specified for crm_report:

      -f, --from time
              time to start from: "YYYY-M-D H:M:S"  (do not forget the quotes)

       -t, --to time
              time to finish at (default: now)


"man crm_report" has all the details

Comment 11 errata-xmlrpc 2013-11-21 22:41:44 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.

http://rhn.redhat.com/errata/RHBA-2013-1688.html