Bug 1325831
Summary: | gluster snap status xml output shows incorrect details when the snapshots are in deactivated state | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Avra Sengupta <asengupt> | |
Component: | snapshot | Assignee: | Avra Sengupta <asengupt> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | aloganat, bugs, rjoseph, storage-qa-internal | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.9.0 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1325821 | |||
: | 1369363 1369372 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-27 18:25:08 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1325821 | |||
Bug Blocks: | 1369363, 1369372 |
Description
Avra Sengupta
2016-04-11 10:34:06 UTC
REVIEW: http://review.gluster.org/14018 (snapshot/cli: Fix snapshot status xml output) posted (#1) for review on master by Avra Sengupta (asengupt) REVIEW: http://review.gluster.org/14018 (snapshot/cli: Fix snapshot status xml output) posted (#2) for review on master by Avra Sengupta (asengupt) COMMIT: http://review.gluster.org/14018 committed in master by Rajesh Joseph (rjoseph) ------ commit efbae0fef5399a8826782b02140f44edaea0dac3 Author: Avra Sengupta <asengupt> Date: Tue Apr 12 12:26:54 2016 +0530 snapshot/cli: Fix snapshot status xml output 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 Change-Id: I99563e8f3e84f1aaeabd865326bb825c44f5c745 BUG: 1325831 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/14018 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/ |