Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 856673 - Add sos to Red Hat Storage
Add sos to Red Hat Storage
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: sos (Show other bugs)
2.0
Unspecified Unspecified
high Severity medium
: ---
: ---
Assigned To: Raghavendra Bhat
Sachidananda Urs
: FutureFeature
Depends On: 855265
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-12 10:43 EDT by Scott Haines
Modified: 2015-01-22 10:30 EST (History)
12 users (show)

See Also:
Fixed In Version: sos-2.2-17.1.el6rhs.noarch.rpm
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 855265
Environment:
Last Closed: 2012-11-12 13:47:20 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1456 normal SHIPPED_LIVE Low: Red Hat Storage 2.0 security, bug fix, and enhancement update #3 2012-11-12 18:46:48 EST

  None (edit)
Comment 4 Amar Tumballi 2012-10-15 07:31:29 EDT
check the sos version on the machine, and it should have rhs in it to confirm the different RPM in our child channel.

changelog in rpm:

-----
Changelog:
* Tue Sep 11 2012 Amar Tumballi <atumball@redhat.com> = 2.2-17.el6rhs.1
- Change gluster.py to send signal to glusterfs process
   directly instead of 'gluster volume status' command.
   Resolves: bz851175
- Capture statedump files in sosreport

-----
Comment 5 Raghavendra Bhat 2012-10-15 08:43:50 EDT
the changes that have been made to sosreport gluster plugin are

* send SIGUSR1 signal to all the glusterfs processes instead of volume statedump or volume status cli command.(with SIGUSR1, from all the glusterfs processes including the mount points, self-heal daemon, nfs server the statedump information is received).

* All the statedump information is collected in the sosreport.
Comment 6 Bryn M. Reeves 2012-10-15 08:50:55 EDT
Please could someone post the patches for this feature to the sos-devel mailing list for review. As we discussed previously we do not want sos in RHS to diverge from upstream and it's important that the review starts early to ensure that we don't end up having to back things out at a later stage.
Comment 7 Sachidananda Urs 2012-10-16 05:49:39 EDT
I guess this is not part of update 3. I still see glusterdumps not being part of the archive.
Comment 8 Amar Tumballi 2012-10-16 05:52:05 EDT
http://pkgs.devel.redhat.com/cgit/rpms/sos/commit/?h=rhs-2.0-rhel-6&id=705f21a7394717d810cca63573cb0b815abd54fa

will make sure we post all the patches to sos-devel@ ML in future.
Comment 9 Amar Tumballi 2012-10-16 05:53:25 EDT
@Sac (for comment #7) did you do a yum upgrade of sos package? sos is a different RPM, and not part of glusterfs rpm set... Refer to one of the mail I have sent to storage-qa on sos package.
Comment 10 Sachidananda Urs 2012-10-16 05:59:09 EDT
Amar, yes I had done yum update before this. Or is it that I download and sosreport separately? Do we have the sosreport version so that I can cross check. I am running:


[root@rhs-client19 ~]# sosreport -v

sosreport (version 2.2)
Comment 11 Sachidananda Urs 2012-10-17 03:23:09 EDT
Verified with RPM: http://download.devel.redhat.com/brewroot/packages/sos/2.2/17.1.el6rhs/noarch/sos-2.2-17.1.el6rhs.noarch.rpm

With the above RPM update sosreport now places the glusterdumps in sosreport archive under directory tmp/ in the archive.
Comment 13 Sachidananda Urs 2012-10-17 07:04:56 EDT
I have opened another bug (https://bugzilla.redhat.com/show_bug.cgi?id=867346) to track where the glusterdump files go into. We will keep this bug in verified state.
Comment 15 errata-xmlrpc 2012-11-12 13:47:20 EST
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/RHSA-2012-1456.html

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