[Bugs] [Bug 1369372] gluster snap status xml output shows incorrect details when the snapshots are in deactivated state

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15291 committed in release-3.8 by Rajesh
Joseph (rjoseph at redhat.com) 
------
commit 106a107ec5c8ecc48c3e048a9b8ad9ac809e278d
Author: Avra Sengupta <asengupt at redhat.com>
Date:   Tue Apr 12 12:26:54 2016 +0530

    snapshot/cli: Fix snapshot status xml output

        Backport of http://review.gluster.org/#/c/14018/

    snap status --xml errors out if a brick is down and
    doesn't have pid. It is handled in the cli of the snap
    status where "N/A" is displayed in such a scenario.
    Handled the same in xml

    snap status <snapname> --xml fails as the writer is
    not initialised for the same. Using GF_SNAP_STATUS_TYPE_ITER
    instead of GF_SNAP_STATUS_TYPE_SNAP for all snap's
    status to differentiate between the two scenarios.

    Added testcase volume-snapshot-xml.t to check
    all snapshot commands xml outputs

    > Reviewed-on: http://review.gluster.org/14018
    > 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: Rajesh Joseph <rjoseph at redhat.com>

    Change-Id: I99563e8f3e84f1aaeabd865326bb825c44f5c745
    BUG: 1369372
    Signed-off-by: Avra Sengupta <asengupt at redhat.com>
    Reviewed-on: http://review.gluster.org/15291
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Rajesh Joseph <rjoseph 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=qGE1SfSkBZ&a=cc_unsubscribe