Bug 983392
Summary: | grammar error in "volume sync" command | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | spandura |
Component: | glusterd | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
Status: | CLOSED EOL | QA Contact: | storage-qa-internal <storage-qa-internal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | rhs-bugs, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | glusterd | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-03 17:15:35 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: |
Description
spandura
2013-07-11 06:40:58 UTC
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. |