[Bugs] [Bug 1185322] New: Enabling SSL for glusterd will cause all nodes to crash when connection is interrupted

[bugzilla at redhat.com]

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

            Bug ID: 1185322
           Summary: Enabling SSL for glusterd will cause all nodes to
                    crash when connection is interrupted
           Product: GlusterFS
           Version: 3.6.1
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: michael at wikberg.fi
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 983340
  --> https://bugzilla.redhat.com/attachment.cgi?id=983340&action=edit
glusterd log

Description of problem:

Added SSL support for volumes (client.ssl on, server.ssl on) and management
(touch /var/lib/glusterd/secure-access), and after the initial successful
restart of all glusterd instances, they all crashed one a single connection was
reset.

Tried with several OpenSSL and GlusterFS version combinations, but the reason
seems to be priv->ssl_ssl being NULL when passed to libssl functions.

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

3.6.1, 3.6.2 7.3dev

How reproducible:
Set up SSL everywhere, wait until a single conenction fail (or glusterd
instance is restarted)

Steps to Reproduce:
1.
2.
3.

Actual results:
If any glusterd instance is unavailable, the glusterd instance will crash
leading to all other connected instances to crash.

Expected results:
Nodes are reconnected after connection failure.


Additional info:
Managed to get nodes online again after adding a check for priv->ssl_ssl ==
NULL in socket.c: ssl_do ssl_teardown_connection

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