[Bugs] [Bug 1470495] gluster volume status --xml fails when there are 100 volumes

[bugzilla at redhat.com]

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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17766 committed in release-3.8 by Niels de
Vos (ndevos at redhat.com) 
------
commit b7b13c8cd295fa2e9fba9cc77211e576469e9581
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Wed Jul 5 14:58:50 2017 +0530

    cli/xml: fix return handling

    The return code of xmlTextWriter* APIs says it returns either the bytes
    written (may be 0 because of buffering) or -1 in case of error. Now if the
    volume of the xml data payload is not huge then most of the time the
    data to be written gets buffered, however when this grows sometimes this
    APIs will return the total number of bytes written and then it becomes
    absolutely mandatory that every such call is followed by
    XML_RET_CHECK_AND_GOTO otherwise we may end up returning a non zero ret
    code which would result into the overall xml generation to fail.

    >Reviewed-on: https://review.gluster.org/17702
    >Smoke: Gluster Build System <jenkins at build.gluster.org>
    >Reviewed-by: Amar Tumballi <amarts at redhat.com>
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    >Reviewed-by: Gaurav Yadav <gyadav at redhat.com>

    Change-Id: I02ee7076e1d8c26cf654d3dc3e77b1eb17cbdab0
    BUG: 1470495
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: https://review.gluster.org/17766
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=LpQoVVX50o&a=cc_unsubscribe