[Bugs] [Bug 1298076] New: Gluster crashes when adding volume with wrong brick hostnames

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1298076

            Bug ID: 1298076
           Summary: Gluster crashes when adding volume with wrong brick
                    hostnames
           Product: GlusterFS
           Version: 3.7.6
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: arik.mitschang at sbibits.com
                CC: bugs at gluster.org



Description of problem:

I have a 4 node gluster setup for use with oVirt and was adding the iso domain.
When I did so, I accidentally used a script from different environment with the
wrong hostnames. All other paramters were correct, just the hostnames of each
brick in the new replica 2 volume I was trying to add.

I corrected the error and tried to add it again, but at that point glusterd
processes on two servers had crashed, and those nodes had come out of the
cluster in peer status. The fix was to remove the /var/lib/glusterd on those
nodes and re-probe, but not before causing a fair amount of chaos.

Version-Release number of selected component (if applicable):

3.7.6


How reproducible:

Unfortunately I cannot tell. Our development environment has somehow become too
critical. Will reproduce time permitting

Steps to Reproduce:
1. Add new volume but misspell brick hostname
2. Add same volume but with correct hostname

Actual results:
gluster crashes on at least some servers

Expected results:
An client error message is returned indicating hosts are not peers in cluster,
but otherwise nothing.

Additional info:

Servers are up-to-date CentOS-7.1.1503 linux 3.10.0-229.20.1.el7.x86_64 on DELL
R730 with recent firmware updates

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.