Bug 867346

Summary: glusterdumps collected by sosreport should go into proper directories
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sachidananda Urs <sac>
Component: sosAssignee: Raghavendra Bhat <rabhat>
Status: CLOSED ERRATA QA Contact: Sachidananda Urs <surs>
Severity: medium Docs Contact:
Priority: high    
Version: 2.0CC: amarts, bmr, rhs-bugs, shaines, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: sos-2.2_17.2.el6rhs Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 880900 (view as bug list) Environment:
Last Closed: 2013-09-23 22:25:55 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: 880900    

Description Sachidananda Urs 2012-10-17 11:04:10 UTC 
Description of problem:

Currently the glusterdumps are stored in directory tmp/, however this needs to be changed as per comments from Bryn M. Reeves.

Quoting his comments:

"""
tmp/ is the wrong place to put them - this is the kind of thing that upstream review is supposed to catch.

We try very hard to avoid dropping files in odd locations - output generated by commands run by sos should go into the appropriate sos_commands/$module directory.

The problem that this creates if it is released to customers is that people building tools on top of sos data have to add hacks to deal with these non-standard locations just in case someone is running an affected sos package.
"""
Comment 2 Amar Tumballi 2012-10-23 18:03:23 UTC 
posted patch @ https://www.redhat.com/archives/sos-devel/2012-October/msg00000.html upon review will commit the fix to RHS channel..
Comment 3 Amar Tumballi 2012-11-26 03:56:02 UTC 
merged and available for testing.
Comment 4 Sachidananda Urs 2012-11-26 05:28:48 UTC 
Now sosreport -e gluster puts the output in sos_commands/gluster which is what is expected.
Comment 5 Scott Haines 2013-09-23 22:25:55 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-1262.html