Bug 849298 - gluster volume rebalance status --xml ouputs wrong xml structure
gluster volume rebalance status --xml ouputs wrong xml structure
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Kaushal
Depends On: 845561
Blocks: 858465
  Show dependency treegraph
Reported: 2012-08-17 22:11 EDT by Vidya Sakar
Modified: 2013-09-23 18:33 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.4.0qa5-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 845561
: 858465 (view as bug list)
Last Closed: 2013-09-23 18:33:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vidya Sakar 2012-08-17 22:11:25 EDT
+++ This bug was initially created as a clone of Bug #845561 +++

current output is
                                    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"?>

expected output is
Comment 2 Kaushal 2012-10-10 03:22:44 EDT
Patch for upstream/master under review at http://review.gluster.org/3869
Comment 3 Kaushal 2012-10-11 23:51:17 EDT
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 .
Comment 7 Prasanth 2013-01-10 06:02:49 EST
Verified in glusterfs-3.4.0qa5-1

# gluster volume rebalance fromclirep status --xml 
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
Comment 9 Scott Haines 2013-09-23 18:33:07 EDT
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.


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