Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 557851

Summary: Sosreport plugin to collect the "M" part in MRG
Product: Red Hat Enterprise Linux 5 Reporter: Ranjith Rajaram <rrajaram>
Component: sosAssignee: Adam Stokes <astokes>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: ablum, agk, ahecox, azelinka, bmr, gsim, jeder, jwest, mflitter
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:07:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
qpidd.py.patch
none
updated patch
none
patch
none
patch
none
patch none

Description Ranjith Rajaram 2010-01-22 17:47:35 UTC 
Description of problem:

Sosreport plugin to collect the "M" part in MRG

Plugin will collect the following from the Broker

1. check whether qpidd packages are installed and will collect the default configuration file
2. Will collect the following command outputs from the broker and will be saved under sos_command/broker/ in the sosreport
   
  qpid-stat [-b/-e/-q]
   


Version-Release number of selected component (if applicable):

sos-1.7-9.43

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:

Does not collect Messaging information

Expected results:

Collect the default configuration commands

Additional info:
Comment 1 Ranjith Rajaram 2010-01-22 17:48:36 UTC 
Created attachment 386209 [details]
qpidd.py.patch
Comment 2 Jeremy Eder 2010-02-09 17:41:27 UTC 
looks to already be a mrg messaging plugin...

that plugin (mrgmessg.py) already grabs:

        self.addCopySpec("/etc/qpidd.conf")
        self.addCopySpec("/etc/sasl2/qpidd.conf")
        self.addCopySpec("/var/rhm")

then this patch (qpidd.py.patch) grabs:

        self.addCopySpec("/etc/qpidd.conf")
        self.collectExtOutput("/usr/bin/qpid-stat -q")
        self.collectExtOutput("/usr/bin/qpid-stat -e")
        self.collectExtOutput("/usr/bin/qpid-stat -b")

do you also want to grab these ?

        self.addCopySpec("/var/lib/qpid/syslog")
        self.addCopySpec("/var/lib/qpid/systemId")
        self.collectExtOutput("/usr/bin/qpid-config")
        self.collectExtOutput("/usr/bin/qpid-config -b exchanges")
        self.collectExtOutput("/usr/bin/qpid-config -b queues")
        self.collectExtOutput("/usr/bin/qpid-stat -c")
Comment 3 Gordon Sim 2010-02-09 18:07:25 UTC 
The syslog might certainly be useful, the systemId in general less so. Most of the info in those extra qpid-config commands would already be obtainable from the qpid-stats in qpidd.py.patch, they do add details of any extra configuration properties and the top-level summary of counts could be convenient as a snapshot so there is probably no harm in adding them in. Note that those commands would error if the service wasn't running.
Comment 4 Jeremy Eder 2010-02-11 17:01:55 UTC 
should we also grab the jinf meta-data files that describe each durable queue ?  is there some other way of finding out the command used to create a durable queue while the broker is not running ?
Comment 5 Jeremy Eder 2010-02-11 19:41:03 UTC 
if certain problems are client-language or otherwise client specific, then we need to collect data about the client via sosreport:

client version
client os
client language
Comment 7 Jeremy Eder 2010-02-15 15:32:32 UTC 
Created attachment 394339 [details]
updated patch
Comment 16 Adam Stokes 2010-03-05 18:32:24 UTC 
Created attachment 398090 [details]
patch
Comment 17 Adam Stokes 2010-03-05 18:33:08 UTC 
Jeremy,

Please verify attached patch satisfies requirements for running the commands in setup method.

Thanks,
Adam
Comment 19 Adam Stokes 2010-03-05 18:54:41 UTC 
Created attachment 398096 [details]
patch
Comment 20 Adam Stokes 2010-03-05 18:55:21 UTC 
Hi Jeremy,

Could you test this attached patch? I re-ran it through pylint and no errors are coming up so hopefully it will load.

Thanks,
Adam
Comment 21 Adam Stokes 2010-03-05 19:37:36 UTC 
Patch tested on mrg system; seems to work.
Comment 24 Adam Stokes 2010-03-08 15:28:13 UTC 
Created attachment 398544 [details]
patch
Comment 25 Adam Stokes 2010-03-08 15:28:48 UTC 
Jeremy/Andrew,

Please have a look at latest attachment to see if the new additions are appropriate.

Thanks,
Adam
Comment 26 Jeremy Eder 2010-03-08 15:42:30 UTC 
Looks good.

--jer
Comment 29 errata-xmlrpc 2010-03-30 08:07:11 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0201.html