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>
Marking this bug for a known-issue
upstream patch available http://review.gluster.org/11491 . will clone to downstream.
Doc text is edited. Please sign off to be included in Known Issues.
hi monti, this doc text looks good to me.
Slightly modified the text.
upstream patch merged: http://review.gluster.org/11491
with the fix, Able to create the shared storage with/without mentioning the domain (cluster) that is, >>gluster volume set all cluster.enable-shared-storage enable (OR) >>gluster volume set all enable-shared-storage enable RHGS version used is = glusterfs-3.7.5-0.3. With above details moving this bug to verified state.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html