Bug 1045374

Summary: 'gluster volume status --xml' has issues
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: glusterfsAssignee: Kaushal <kaushal>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: high Docs Contact:
Priority: high    
Version: 2.1CC: dtsang, grajaiya, knarra, mmahoney, pprakash, sdharane, vagarwal, vbellur
Target Milestone: ---Keywords: Regression, ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.53rhs Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1046020 (view as bug list) Environment:
Last Closed: 2014-02-25 08:09:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1046020    
Bug Blocks: 1021441    

Description Shruti Sampat 2013-12-20 09:50:07 UTC
Description of problem:
-------------------------

The following is from the output of "gluster volume status --xml" command - 

-------
          <node>
             <node>
               <hostname>NFS Server</hostname>
               <path>localhost</path>
<peerid>63ca3d2f-8c1f-4b84-b797-b4baddab81fb</peerid>
               <status>1</status>
               <port>2049</port>
               <pid>2130</pid>
             </node>
-----

The xml tag <node> is nested as seen above.

Version-Release number of selected component (if applicable):
glusterfs 3.4.0.50rhs

How reproducible:
Always

Steps to Reproduce:
1. Run the "gluster volume status --xml" command for a distributed-replicate volume.

Actual results:
The <node> tag is nested as seen above.

Expected results:
<node> tag should not be nested.

Additional info:

Comment 4 Shruti Sampat 2014-01-03 06:37:36 UTC
Verified as fixed in glusterfs-3.4.0.53rhs.

Comment 6 errata-xmlrpc 2014-02-25 08:09:48 UTC
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.

http://rhn.redhat.com/errata/RHEA-2014-0208.html