Bug 983392 - grammar error in "volume sync" command
grammar error in "volume sync" command
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
Depends On:
  Show dependency treegraph
Reported: 2013-07-11 02:40 EDT by spandura
Modified: 2015-12-03 12:15 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-03 12:15:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description spandura 2013-07-11 02:40:58 EDT
Description of problem:

Currently the "volume sync" command is syntax: 
volume sync <HOSTNAME> [all|<VOLNAME>] - sync the volume information from a peer

This means, volume sync <HOSTNAME> can be used with 2 options "all" and "VOLNAME".

Expected behavior:
1. volume sync <HOSTNAME> should be used with 2 options either "all" or "VOLNAME". Hence the options can't be inside square braces []. 

2. As per the discussion with developer, "all" option is not working. Either we should be removing this "all" option from the command or document about not to use "all" option. 

Version-Release number of selected component (if applicable):
root@king [Jul-11-2013-12:09:42] >gluster --version
glusterfs built on Jul  6 2013 14:35:18

root@king [Jul-11-2013-12:10:02] >rpm -qa | grep glusterfs-server
Comment 2 spandura 2013-07-11 05:23:40 EDT
Expected Behavior:
3. Currently , the volume sync command has to be executed on the node which requires sync. 

General understand about any volume command is that, the volume commands can be executed from any of the storage node in the cluster. But this command has to be specifically executed on the node which requires volume information to be synced. 

This is quiet confusing.
Comment 3 spandura 2013-07-11 07:34:34 EDT
The "Expected Behavior 2" mentioned in description of the problem doesn't hold good as the option "all" is working. 

Tested this option i.e "gluster volume sync <node> all" as part of testing the bug "https://bugzilla.redhat.com/show_bug.cgi?id=865700". This is working fine now. 

Verified on build:
root@king [Jul-11-2013-17:03:11] >gluster --version
glusterfs built on Jul  6 2013 14:35:18

root@king [Jul-11-2013-17:03:16] >rpm -qa | grep glusterfs-server
Comment 4 Vivek Agarwal 2015-12-03 12:15:35 EST
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.

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