+++ 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@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@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.
REVIEW: http://review.gluster.org/11835 (xml output: Fix non-uniform opErrstr xml output) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/11835 (xml output: Fix non-uniform opErrstr xml output) posted (#2) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/11835 committed in master by Rajesh Joseph (rjoseph) ------ commit 37353199483f2052b50e9d0b35257c27a08f3da4 Author: Avra Sengupta <asengupt> Date: Wed Aug 5 16:36:06 2015 +0530 xml output: Fix non-uniform opErrstr xml output Display <opErrstr/> in case of no operrstr for all xml output of gluster commands. Change-Id: Ie16f749f90b4642357c562012408c434cd38661f BUG: 1245895 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11835 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: mohammed rafi kc <rkavunga> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user