Bug 845559 - gluster volume rebalance stop --xml outputs wrong xml structure
Summary: gluster volume rebalance stop --xml outputs wrong xml structure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 849297 858464
TreeView+ depends on / blocked
 
Reported: 2012-08-03 12:36 UTC by Bala.FA
Modified: 2015-11-23 02:57 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 849297 (view as bug list)
Environment:
Last Closed: 2013-07-24 17:49:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Bala.FA 2012-08-03 12:36:51 UTC
gluster volume rebalance stop --xml outputs 
                                    Node Rebalanced-files          size       scanned      failures         status run time in secs
                               ---------      -----------   -----------   -----------   -----------   ------------    -----------
                               localhost                0            0            0            0      completed           1.00
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput><opRet>0</opRet><opErrno>3</opErrno><opErrstr></opErrstr><cliOp>volRebalance</cliOp><output>Stopped rebalance process on volume test1 
</output></cliOutput>


Expected output is
<cliOutput><opRet>0</opRet><opErrno>3</opErrno><opErrstr></opErrstr><cliOp>volRebalance</cliOp><output>Stopped rebalance process on volume test1 
</output></cliOutput>

Comment 1 Kaushal 2012-10-10 07:21:02 UTC
Patch under review at http://review.gluster.org/3869

Comment 2 Kaushal 2012-10-12 03:50:10 UTC
Fixed by commit f1f3d1c (cli: Changes and enhancements to XML output) for bug https://bugzilla.redhat.com/show_bug.cgi?id=828131 . Reviewed at http://review.gluster.org/3869 .


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