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.
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):
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
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
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