[Bugs] [Bug 1218732] New: gluster volume status --xml gives back unexpected non xml output

bugzilla at redhat.com bugzilla at redhat.com
Tue May 5 17:13:12 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1218732

            Bug ID: 1218732
           Summary: gluster volume status --xml gives back unexpected non
                    xml output
           Product: GlusterFS
           Version: 3.6.2
         Component: cli
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: kauffman at cs.uchicago.edu
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
Command 'gluster snapshot status --xml' outputs text that is not part of the
xml. This inconsistency breaks my code which only has a reason to expect xml
data as input.

Version-Release number of selected component (if applicable):
Seen in 3.6.2.

How reproducible:
Always.

Steps to Reproduce: 
1. Create at least a 2 node cluster.
2. Create 1 volume.
3. Make sure you don't have any snapshots.

Actual results:
root at gfs-test-1:~# gluster snapshot status --xml
No snapshots present
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
  <opRet>0</opRet>
  <opErrno>0</opErrno>
  <opErrstr>(null)</opErrstr>
  <snapStatus>
    <snapshots/>
  </snapStatus>
</cliOutput> 

Expected results:
root at gfs-test-1:~# gluster snapshot status --xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
  <opRet>0</opRet>
  <opErrno>0</opErrno>
  <opErrstr>(null)</opErrstr>
  <snapStatus>
    <snapshots/>
  </snapStatus>
</cliOutput> 


Additional info:
Is this 'null' in the output on purpose? 
  <opErrstr>(null)</opErrstr> 
Other commands like 'gluster snapshot info --xml' show '<opErrstr/>'.


I am marking this as high priority since I parse this output and expect the
output to be consistent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list