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.
Description of problem:
The man page for crm_report suggests an output directory can be passed with --dest:
--dest a custom destination directory/file
When crm_report is run from another data collector tool (e.g. sosreport) it's desirable to have the output written into a directory and not packaged into a tar archive.
This avoids the need to create a tar archive with crm_report and then unpack it into the other tool's archive directory, or to including one tarball inside another (this is something we try to avoid as it complicates handling of reports by data consumers).
Version-Release number of selected component (if applicable):
pacemaker-1.1.8-7.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. crm_report -S --dest=/tmp/foo --from $DATE
Actual results:
/tmp/foo.tar.bz2 is created
Expected results:
Option available to set destination to be a directory and to skip tar archive creation.
Additional info:
You can achieve this with the existing packages by adding -d to the command line.
For some reason it is not in the help text (but it wont be going away because I use it every day :-)
Description of problem: The man page for crm_report suggests an output directory can be passed with --dest: --dest a custom destination directory/file When crm_report is run from another data collector tool (e.g. sosreport) it's desirable to have the output written into a directory and not packaged into a tar archive. This avoids the need to create a tar archive with crm_report and then unpack it into the other tool's archive directory, or to including one tarball inside another (this is something we try to avoid as it complicates handling of reports by data consumers). Version-Release number of selected component (if applicable): pacemaker-1.1.8-7.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. crm_report -S --dest=/tmp/foo --from $DATE Actual results: /tmp/foo.tar.bz2 is created Expected results: Option available to set destination to be a directory and to skip tar archive creation. Additional info: