Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 782588 - sosreport cluster module - hide libxml2 debug output
sosreport cluster module - hide libxml2 debug output
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sos (Show other bugs)
5.8
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Bryn M. Reeves
David Kutálek
: EasyFix
Depends On:
Blocks: 1049888 1098793
  Show dependency treegraph
 
Reported: 2012-01-17 14:54 EST by David Kutálek
Modified: 2014-10-15 23:41 EDT (History)
6 users (show)

See Also:
Fixed In Version: sos-1.7-9.67.el5
Doc Type: Bug Fix
Doc Text:
no docs needed
Story Points: ---
Clone Of:
: 1098793 (view as bug list)
Environment:
Last Closed: 2014-09-15 20:31:13 EDT
Type: ---
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 RHBA-2014:1200 normal SHIPPED_LIVE sos bug fix update 2014-09-16 00:17:05 EDT

  None (edit)
Description David Kutálek 2012-01-17 14:54:36 EST
Description of problem:

On RHEL5 in cluster module, libxml2 is used to parse /etc/cluster/cluster.conf. When encountering badly formed xml config, libxml2 prints parsing debug info, which would be better to hide before user. It should be possible by redefinition od error handling routines.

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

sos-1.7-9.62.el5

How reproducible:

Always

Steps to Reproduce:
1. Corrupt /etc/cluster/cluster.conf somehow
2. sosreport -o cluster
3.
  
Actual results:

libxml2 debuggin info is printed

Expected results:

would be better to not print it

Additional info:
Comment 1 RHEL Product and Program Management 2012-06-11 21:17:53 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 2 Bryn M. Reeves 2014-02-14 10:45:44 EST
# echo CRUNCH > /etc/cluster/cluster.conf
# sosreport --batch -o cluster

sosreport (version 1.7)

This utility will collect some detailed  information about the
hardware and  setup of your  Red Hat Enterprise Linux  system.
The information is collected and an archive is  packaged under
/tmp, which you can send to a support representative.
Red Hat will use this information for diagnostic purposes ONLY
and it will be considered confidential information.

This process may take a while to complete.
No changes will be made to your system.


/etc/cluster/cluster.conf:1: parser error : Start tag expected, '<' not found
CRUNCH
^
One or more plugins have detected a problem in your configuration.
Please review the following messages:

cluster:
    * required module is not loaded: dlm
    * service cman is not running
    * service cman is not started in default runlevel
    * service rgmanager is not running
    * service rgmanager is not started in default runlevel
    * cluster node is not quorate
    * /etc/cluster/cluster.conf contains malformed XML

 plugin cluster finished ...                   
 Completed.

Creating compressed archive...

Your sosreport has been generated and saved in:
  /tmp/sosreport-rhel5-vm1-836658-baf014.tar.bz2

The md5sum is: 4c9837065776a8aa2e57b894a7baf014

Please send this file to your support representative.
Comment 6 errata-xmlrpc 2014-09-15 20:31:13 EDT
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-2014-1200.html

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