Description of problem: when there are large number of volumes in my case 100 volumes, gluster v status --xml command fails Version-Release number of selected component (if applicable): glusterfs-3.8.4-18.el7rhgs.x86_64 How reproducible: 100% Steps to Reproduce: 1. create 100 volume 2. execure gluster v status --xml 3. Actual results: [root@dhcp46-22 ~]# gluster v status all clients --xml [root@dhcp46-22 ~]# echo $? 92 Command fails without giving proper xml Expected results: gluster v status --xml should xml output of command Additional info:
Since this bug is related to customer BZ# 1454544 which has to go in 3.3. Marking this bug as blocker.
upstream patch : https://review.gluster.org/#/c/17702
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/111200
gluster v status all clients --xml works every time when there are 100 volumes. <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <cliOutput> <opRet>0</opRet> <opErrno>0</opErrno> <opErrstr/> <volStatus> <volumes> <volume> <volName>gluster_shared_storage</volName> <nodeCount>3</nodeCount> <node> <hostname>10.70.47.192</hostname> <path>/var/lib/glusterd/ss_brick</path> <peerid>ec9efcbd-a629-4fe8-854d-3ce3c1c30cb6</peerid> <status>1</status> <port>49157</port> <ports> <tcp>49157</tcp> <rdma>N/A</rdma> </ports> <pid>24963</pid> <clientsStatus> <clientCount>2</clientCount> <client> <hostname>10.70.46.22:337</hostname> <bytesRead>1108</bytesRead> <bytesWrite>668</bytesWrite> <opVersion>31101</opVersion> </client> <client> <hostname>10.70.47.56:337</hostname> bug verified on build glusterfs-3.8.4-33.el7rhgs.x86_64
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. https://access.redhat.com/errata/RHBA-2017:2774