Description of problem: "gluster peer probe <hostname> --xml" outputs wrong xml in case of error <?xml version="1.0"?> <cliOutput> <opRet>-1</opRet> <opErrno>107</opErrno> <opErrstr>(null)</opErrstr> <cliOp>peerProbe</cliOp> <output>Probe unsuccessful Probe returned with unknown errno 107</output> </cliOutput> Version-Release number of selected component (if applicable): glusterfs 3.3.0rhsvirt1-8.el6rhs How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: <?xml version="1.0"?> <cliOutput> <opRet>-1</opRet> <opErrno>107</opErrno> <opErrstr>Probe unsuccessful Probe returned with unknown errno 107</opErrstr></cliOutput> Additional info:
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)
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)
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"?> <cliOutput> <opRet>-1</opRet> <opErrno>107</opErrno> <opErrstr>Probe returned with unknown errno 107</opErrstr> </cliOutput> ----------
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-2013-1262.html