*** Bug 1286039 has been marked as a duplicate of this bug. ***
After discussing this with Atin, I am moving this to the glusterd team.
I tried this on RHGS 3.1.2 and did not see any crash. However, the command fails consistently.
[root@localhost ~]# gluster v set dist-vol cluster.extra-hash-regex '(.*)\.swp*'
volume set: failed: Commit failed on localhost. Please check the log file for more details.
The following messages are seen in the glusterd log:
[2016-06-08 05:30:51.400186] E [graph.y:365:graphyyerror] 0-parser: syntax error: line 1271 (volume 'dist-vol-dht'): "dist-vol-client-0"
allowed tokens are 'volume', 'type', 'subvolumes', 'option', 'end-volume'()
[2016-06-08 05:30:51.400263] E [MSGID: 101098] [xlator.c:652:xlator_tree_free_members] 0-parser: Translator tree not found
[2016-06-08 05:30:51.400285] E [MSGID: 101098] [xlator.c:673:xlator_tree_free_memacct] 0-parser: Translator tree not found
[2016-06-08 05:30:51.400357] E [MSGID: 106398] [glusterd-op-sm.c:2655:glusterd_op_set_volume] 0-management: Unable to restart services
[2016-06-08 05:30:51.400378] E [MSGID: 106123] [glusterd-syncop.c:1407:gd_commit_op_phase] 0-management: Commit of operation 'Volume Set' failed on localhost
Based on comment 5, moving it to POST
The observation was this issue was seen in GlusterFS 3.7, but not in GlusterFS 3.8 which means this got fixed as part of a separate change (probably). Given rhgs-3.2.0 is rebased to GlusterFS 3.8.4 this issue shouldn't be seen in rhgs-3.2.0 now, moving the state to Modified.
Verified this bug using the build - glusterfs-3.8.4-2.
Reported issue is not seen with this build.
[root@~]# gluster volume get Dis-Rep cluster.extra-hash-regex
[root@ ~]# gluster v set Dis-Rep cluster.extra-hash-regex '(.*)\.swp*'
volume set: success
[root@ ~]# gluster volume get Dis-Rep cluster.extra-hash-regex
Moving to verified state.
*Note*: I verified this bug from glusterd point
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.