[Bugs] [Bug 1253607] New: gluster snapshot status --xml gives back unexpected non xml output

[bugzilla at redhat.com]

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

            Bug ID: 1253607
           Summary: gluster snapshot status --xml gives back unexpected
                    non xml output
           Product: GlusterFS
           Version: 3.7.3
         Component: snapshot
          Keywords: Triaged
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: asengupt at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    gluster-bugs at redhat.com, kauffman at cs.uchicago.edu
        Depends On: 1218732, 1245895
            Blocks: 1245897



+++ This bug was initially created as a clone of Bug #1245895 +++

+++ This bug was initially created as a clone of Bug #1218732 +++

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.

--- Additional comment from Anand Avati on 2015-08-05 07:12:35 EDT ---

REVIEW: http://review.gluster.org/11835 (xml output: Fix non-uniform opErrstr
xml output) posted (#1) for review on master by Avra Sengupta
(asengupt at redhat.com)

--- Additional comment from Anand Avati on 2015-08-12 04:26:58 EDT ---

REVIEW: http://review.gluster.org/11835 (xml output: Fix non-uniform opErrstr
xml output) posted (#2) for review on master by Avra Sengupta
(asengupt at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1218732
[Bug 1218732] gluster snapshot status --xml gives back unexpected non xml
output
https://bugzilla.redhat.com/show_bug.cgi?id=1245895
[Bug 1245895] gluster snapshot status --xml gives back unexpected non xml
output
https://bugzilla.redhat.com/show_bug.cgi?id=1245897
[Bug 1245897] gluster snapshot status --xml gives back unexpected non xml
output
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.