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

bugzilla at redhat.com bugzilla at redhat.com
Wed Jul 19 21:31:59 UTC 2017


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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17764 committed in release-3.10 by
Raghavendra Talur (rtalur at redhat.com) 
------
commit 470889caeb67c8e5874f19867879104c9fc73a8f
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: 1470488
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: https://review.gluster.org/17764
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra Talur <rtalur 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=NoFfGORHmF&a=cc_unsubscribe


More information about the Bugs mailing list