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 3.4.0.12rhs.beta3 built on Jul 6 2013 14:35:18 root@king [Jul-11-2013-12:10:02] >rpm -qa | grep glusterfs-server glusterfs-server-3.4.0.12rhs.beta3-1.el6rhs.x86_64
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.
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 3.4.0.12rhs.beta3 built on Jul 6 2013 14:35:18 root@king [Jul-11-2013-17:03:16] >rpm -qa | grep glusterfs-server glusterfs-server-3.4.0.12rhs.beta3-1.el6rhs.x86_64
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.