Bug 855265

Summary:	sosreport enhancements for RHS 2.1
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vidya Sakar <vinaraya>
Component:	sos	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED ERRATA	QA Contact:	Sachidananda Urs <surs>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	2.0	CC:	amarts, bmr, rfortier, rhs-bugs, sac, shaines
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0qa5-1	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	856673 (view as bug list)		Environment:
Last Closed:	2013-09-23 22:29: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:	856673

Description Vidya Sakar 2012-09-07 07:21:33 UTC

This BZ is to track all the improvements planned for sosreport in RHS 2.1
  - Adding all the new supportability options which gets added in 2.1
  - Packaging sosreport in RHS child channel. With the frequency and velocity of change happening in RHS, it is getting difficult to align with the timeline requirements of integrating the changes in RHEL sosreport much in advance.

Comment 2 Amar Tumballi 2012-10-05 16:57:20 UTC

http://download.devel.redhat.com/brewroot/packages/sos/2.2/17.1.el6rhs/noarch/sos-2.2-17.1.el6rhs.noarch.rpm 

RPM built with the required changes, will just need to release it...

Comment 3 Sachidananda Urs 2013-01-09 09:43:55 UTC

* Package name changed to comply to conventions.
* Gluster dumps have start and end markers to identify that the dump is not garbled.
* Gluster dumps go to proper directory in the sosreport dump.
* Gluster dumps have timestamps in their file names so that the future gluster dumps are not overwritten.

Comment 6 Scott Haines 2013-09-23 22:29: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