[Bugs] [Bug 1392181] [GSS]"gluster vol status all clients --xml" get malformed at times, causes gstatus to fail

[bugzilla at redhat.com]

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



--- Comment #1 from Giuseppe Ragusa <giuseppe.ragusa at hotmail.com> ---
Verified on GlusterFS 3.7.16 (CentOS Storage SIG packages):

[root at shockley ~]# gluster vol status all clients
Client connections for volume ctdb
----------------------------------------------
Brick : read.gluster.private:/srv/glusterfs/disk0/ctdb_brick
Clients connected : 3
Hostname                                               BytesRead   
BytesWritten
--------                                               ---------   
------------
172.25.5.21:49125                                           1032            
624
172.25.5.22:49127                                         199404         
177816
172.25.5.23:49116                                           1020            
624
----------------------------------------------
Brick : hall.gluster.private:/srv/glusterfs/disk0/ctdb_brick
Clients connected : 3
Hostname                                               BytesRead   
BytesWritten
--------                                               ---------   
------------
172.25.5.21:49122                                           1032            
624
172.25.5.23:49114                                         199404         
177816
172.25.5.22:49124                                           1020            
624
----------------------------------------------
Brick : shockley.gluster.private:/srv/glusterfs/disk0/ctdb_arbiter_brick
Clients connected : 3
Hostname                                               BytesRead   
BytesWritten
--------                                               ---------   
------------
172.25.5.21:49112                                         199428         
180340
172.25.5.23:49034                                           1032            
648
172.25.5.22:49049                                           1032            
648
----------------------------------------------
...
(Output cut for brevity)
[root at shockley ~]# echo $?
0
[root at shockley ~]# gluster vol status all clients --xml
[root at shockley ~]# echo $?
96
[root at shockley ~]# gstatus

Traceback (most recent call last):e
  File "/bin/gstatus", line 221, in <module>
    main()
  File "/bin/gstatus", line 135, in main
    cluster.update_state(self_heal_backlog)
  File "/usr/lib/python2.7/site-packages/gstatus/libgluster/cluster.py", line
542, in update_state
    cmd.run()
  File "/usr/lib/python2.7/site-packages/gstatus/libcommand/glustercmd.py",
line 100, in run
    xmldoc = ETree.fromstring(''.join(self.stdout))
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1301, in XML
    return parser.close()
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1654, in close
    self._raiseerror(v)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in
_raiseerror
    raise err
xml.etree.ElementTree.ParseError: no element found: line 1, column 0

I didn't find any trace of the 3.8.x fixes being backported on 3.6.17 or newer,
sorry if I missed something.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.