Description of problem: [root@dhcp43-153 ~]# gluster v create rep arbiter 3 10.70.43.153:/rhs/brick{1..3}/brick force gluster: cli-cmd-parser.c:632: cli_cmd_volume_create_parse: Assertion `!"opword mismatch"' failed. Aborted (core dumped) [root@dhcp43-153 ~]# Version-Release number of selected component (if applicable): glusterfs --version glusterfs 3.9dev built on Jun 8 2016 14:50:20 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2013 Red Hat, Inc. <http://www.redhat.com/> GlusterFS comes with ABSOLUTELY NO WARRANTY. It is licensed to you under your choice of the GNU Lesser General Public License, version 3 or any later version (LGPLv3 or later), or the GNU General Public License, version 2 (GPLv2), in all cases as published by the Free Software Foundation. How reproducible: 100% Steps to Reproduce: Don't give "replica 3" 1. gluster v create rep arbiter 3 10.70.43.153:/rhs 2. 3. Actual results: core dumped Expected results: It should display a message with correct usage help. Additional info:
Are you working on the fix Ashish?
No, I just raised this bug and continued to reproduce other bug on which I was working and found this.
Okay.
REVIEW: http://review.gluster.org/14738 (cli: fix crash in arbiter keyword parsing) posted (#1) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/14738 (cli: fix crash in arbiter keyword parsing) posted (#2) for review on master by Ravishankar N (ravishankar)
COMMIT: http://review.gluster.org/14738 committed in master by Atin Mukherjee (amukherj) ------ commit b5c492dfea2d2e2075aa88d7153fba57b06e739d Author: Ravishankar N <ravishankar> Date: Thu Jun 16 10:21:53 2016 +0530 cli: fix crash in arbiter keyword parsing A negative case like `gluster volume create volname arbiter 3 /bricks{1..3}` must not crash. 'arbiter' keyword is valid only for (3 way) replica volumes. The .t that is added will crash and create a core *without* the fix when run but will still pass all TESTs. Since the regression framework fails the .t if it creates a core, we can consider it a valid test 'that fails without the fix'. Change-Id: Ie2d7ced66025ea3617d30f6f823b22401e6d2fde BUG: 1346821 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/14738 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
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.9.0, please open a new bug report. glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/