Bug 1035778 - add option to disable tar archive creation to crm_report
Summary: add option to disable tar archive creation to crm_report
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pacemaker
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andrew Beekhof
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-28 13:03 UTC by Bryn M. Reeves
Modified: 2014-01-03 14:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-01 23:08:32 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Bryn M. Reeves 2013-11-28 13:03:51 UTC
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:

Comment 2 Andrew Beekhof 2013-12-01 23:08:32 UTC
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 :-)

Comment 3 Bryn M. Reeves 2014-01-03 14:07:03 UTC
Perfect, thanks!


Note You need to log in before you can comment on or make changes to this bug.