Description of problem: When running the command "gluster volume set <volname> group virt" it fails with: volume set: failed: option : eager-lock does not exist Did you mean eager-lock? This is because there is now a 'disperse.eager-lock', so it needs to be explicitly named as 'cluster.eager-lock' in the virt group Version-Release number of selected component (if applicable): 3.7.10-1 How reproducible: Always Steps to Reproduce: 1. As above 2. 3. Actual results: As above Expected results: volume set: success Additional info: Changing the line 'eager-lock=enable' to 'cluster.eager-lock=enable' resolves this
The cause of this issue is that the options and values listed in the virt profile file doesn't include the domain of the option. Its always good to have key along with its domain in the format : "domain.key=value"
The patch - http://review.gluster.org/#/c/13958/ - fixes this issue
REVIEW: http://review.gluster.org/13958 (extras: Add namespace for options in group-virt.example) posted (#3) for review on release-3.7 by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/13958 committed in release-3.7 by Kaushal M (kaushal) ------ commit 2b7ae34eff4ed00f15661cf1ca5b2ee07a1d93bd Author: Vijay Bellur <vbellur> Date: Fri Apr 8 21:59:53 2016 -0400 extras: Add namespace for options in group-virt.example Commit 23ccabbeb7 introduced a new key "disperse.eager-lock" which causes a conflict with key "cluster.eager-lock" when option is used without the qualifying namespace. group-virt.example which gets installed as /var/lib/glusterd/ groups/virt contains options without namespace qualifiers. This patch adds the appropriate namespace to all options in group-virt.example. Change-Id: I2c09dd10d44138410d889ddeb805f01c641c6780 BUG: 1325630 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/13929 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Reviewed-on: http://review.gluster.org/13958 Smoke: Gluster Build System <jenkins.com> Tested-by: Kaushal M <kaushal> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Kaushal M <kaushal>
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.7.11, please open a new bug report. glusterfs-3.7.11 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] https://www.gluster.org/pipermail/gluster-users/2016-April/026321.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
*** Bug 1332550 has been marked as a duplicate of this bug. ***