+++ This bug was initially created as a clone of Bug #1236153 +++ Description of problem: ----------------------- Setting the option, enable-shared-storage, without mentioning the domain 'cluster' doesn't creates the gluster_shared_storage volume Version-Release number of selected component (if applicable): -------------------------------------------------------------- glusterfs-3.7.1-5.el6rhs How reproducible: ------------------ Always Steps to Reproduce: -------------------- 1. Create a volume of any type 2. Enable enable-shared-storage on the volume, without mentioning the domain (i.e) gluster volume set all enable-shared-storage enable Actual results: --------------- Setting enabling the option enable-shared-storage doesn't created the shared gluster volume by name gluster_shared_storage Expected results: ----------------- gluster_shared_storage should be created when enable-shared-storage is enabled Additional info: ---------------- RCA is here. The hook script '/var/lib/glusterd/hooks/1/set/post/S32gluster_enable_shared_storage.sh' checks for the key 'cluster.enable-shared-storage' and exits when the key is 'enable-shared-storage' <snip_from_hook_script> if [ "$key" != "cluster.enable-shared-storage" ]; then exit; fi </snip_from_hook_script>
REVIEW: http://review.gluster.org/11491 (extra: "enable-shared-storage" key should create shared-storage) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
COMMIT: http://review.gluster.org/11491 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 890e58f5d4d3db9477e36cac3d16798ffe3b0480 Author: Gaurav Kumar Garg <ggarg> Date: Wed Jul 1 17:55:47 2015 +0530 extra: "enable-shared-storage" key should create shared-storage Currently while creating shared storage it accept only "cluster.enable-shared-storage" key. It should also accept "enable-shared-storage" key. Change-Id: I4c68782f4b7927ec8cd725e411b0b9db17d9c48d BUG: 1238224 Signed-off-by: Gaurav Kumar Garg <ggarg> Reviewed-on: http://review.gluster.org/11491 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Avra Sengupta <asengupt>
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