Bug 879490 - gluster peer probe --xml outputs wrong xml format
gluster peer probe --xml outputs wrong xml format
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Avra Sengupta
Depends On:
  Show dependency treegraph
Reported: 2012-11-23 02:01 EST by Bala.FA
Modified: 2015-11-22 21:57 EST (History)
6 users (show)

See Also:
Fixed In Version: glusterfs-3.4.0qa8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-23 18:34:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bala.FA 2012-11-23 02:01:40 EST
Description of problem:
"gluster peer probe <hostname> --xml" outputs wrong xml in case of error

<?xml version="1.0"?>
  <output>Probe unsuccessful
Probe returned with unknown errno 107</output>

Version-Release number of selected component (if applicable):
glusterfs 3.3.0rhsvirt1-8.el6rhs

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:
<?xml version="1.0"?>
  <opErrstr>Probe unsuccessful Probe returned with unknown errno 107</opErrstr></cliOutput>

Additional info:
Comment 2 Vijay Bellur 2012-12-18 22:15:27 EST
CHANGE: http://review.gluster.org/4301 (cli: Fixing the xml output in failure cases for gluster peer probe) merged in master by Anand Avati (avati@redhat.com)
Comment 4 Vijay Bellur 2012-12-19 03:49:54 EST
CHANGE: http://review.gluster.org/4335 (cli: Making the op-ret check for gluster peer probe --xml more robust.) merged in master by Vijay Bellur (vbellur@redhat.com)
Comment 5 Prasanth 2013-05-02 02:52:54 EDT
Verified as fixed in glusterfs-3.4.0qa8

# gluster peer probe qa-vm06.lab.eng.blr.redhat.com  --xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <opErrstr>Probe returned with unknown errno 107</opErrstr>
Comment 6 Scott Haines 2013-09-23 18:34:36 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.


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