Bug 1161416 - snapshot delete all command fails with --xml option.
Summary: snapshot delete all command fails with --xml option.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: rjoseph
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1245077 1257533 1258113
TreeView+ depends on / blocked
 
Reported: 2014-11-07 05:27 UTC by Darshan
Modified: 2016-08-16 13:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1245077 1257533 (view as bug list)
Environment:
Last Closed: 2016-08-16 13:06:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Darshan 2014-11-07 05:27:31 UTC
Description of problem:
gluster snapshot delete all command fails when invoked with --xml option.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.gluster snapshot delete all --xml
2.
3.

Actual results:
when above command is executed it fails with message "Snapshot command failed"

Expected results:
command should provide proper xml output.

Additional info:

Comment 1 Darshan 2015-01-23 07:15:46 UTC
Even "gluster snapshot delete volume <volume-name> --xml" command fails

Comment 2 Anand Avati 2015-08-29 10:09:31 UTC
REVIEW: http://review.gluster.org/12043 (gluster/cli: snapshot delete all does not work with xml) posted (#1) for review on release-3.6 by Avra Sengupta (asengupt@redhat.com)

Comment 3 Vijay Bellur 2016-03-21 06:46:12 UTC
REVIEW: http://review.gluster.org/12043 (gluster/cli: snapshot delete all does not work with xml) posted (#2) for review on release-3.6 by Avra Sengupta (asengupt@redhat.com)

Comment 4 Mike McCune 2016-03-28 23:28:22 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 5 Mohammed Rafi KC 2016-08-16 13:06:48 UTC
This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. This bug has been fixed in more recent GlusterFS releases. If you still face this bug with the newer GlusterFS versions, please open a new bug.'


Note You need to log in before you can comment on or make changes to this bug.