Bug 485191 - Sos plugin to Collect Quagga configuration files
Summary: Sos plugin to Collect Quagga configuration files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sos
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Adam Stokes
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-12 08:20 UTC by Ranjith Rajaram
Modified: 2010-03-30 08:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 08:07:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Quagga Patch (1.31 KB, patch)
2009-02-12 11:16 UTC, Ranjith Rajaram
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0201 0 normal SHIPPED_LIVE sosreport bug fix and enhancement update 2010-03-29 12:26:44 UTC

Description Ranjith Rajaram 2009-02-12 08:20:16 UTC
Description of problem:

Plugin to Collect information related with Quagga by grabbing all the configuration files.

Some of our S390x customer do have quagga installed in their system. It would be helpful if we collect the Quagga configuration with sosreport itself.

We do provide Quagga package for all Arch's.  I have attached Sos plugin to capture Quagga related information



How reproducible:


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

does not Collect Quagga related configuration files through sosreport

Expected results:


Collect Quagga related configuration files through sosreport

Additional info:

Comment 1 Ranjith Rajaram 2009-02-12 08:21:45 UTC
Created attachment 331665 [details]
Sos Quagga patch

Comment 2 Ranjith Rajaram 2009-02-12 11:16:24 UTC
Created attachment 331677 [details]
Quagga Patch

Comment 7 errata-xmlrpc 2010-03-30 08:07:46 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


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