+++ This bug was initially created as a clone of Bug #1297442 +++ Description of problem: "gluster vol get volname user.metadata-text" Command is not working. Command fails with the error "volume get option: failed: Did you mean cluster.metadata-self-heal?" Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Create a Volume (any topology) 2. Set a volume description using #gluster vol set <volname> user.metadata-text 'VOLUME DESCRIPTION' 3. Try to read the description using #gluster vol get volname user.metadata-text or #gluster vol get volname all | grep user The volume description is shown in the #gluster volume info. Actual results: Command fails with the below error, "volume get option: failed: Did you mean cluster.metadata-self-heal?" Expected results: Command should return the user.metadata-text --- Additional comment from Atin Mukherjee on 2016-01-11 23:16:37 EST --- user.* bucket is a hooks friendly option and volume get framework only looks for the options from volume map entry (VME) table. This is why volume get never captures it. I'd need to understand the reason of having user.* under hooks, what was the motivation/intention behind it. Based on that we'd update the status accordingly.
REVIEW: http://review.gluster.org/13222 (glusterd: display usr.* options in volume get) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/13222 (glusterd: display usr.* options in volume get) posted (#2) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/13222 (glusterd: display usr.* options in volume get) posted (#3) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/13222 (glusterd: display usr.* options in volume get) posted (#4) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/13222 (glusterd: display user.* options in volume get) posted (#5) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/13222 committed in master by Atin Mukherjee (amukherj) ------ commit 18612a7b2e005d76529f8c2a6149a6506f6daae6 Author: Atin Mukherjee <amukherj> Date: Tue Jan 12 10:41:46 2016 +0530 glusterd: display user.* options in volume get As of now volume get framework doesn't consider user.* xattrs to be displayed. This patch is to include them in volume get output. Please note these options will be only shown for a given volume name, 'all' as a volume name wouldn't consider them displaying. Change-Id: Ifc19e89c612e9254d760deaaef50bc1b4bfe02ce BUG: 1297638 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/13222 CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra Talur <rtalur>
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.8.0, please open a new bug report. glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user