[Bugs] [Bug 1356942] New: Problem with persistant mount on quorum fail when using SSL

[bugzilla at redhat.com]

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

            Bug ID: 1356942
           Summary: Problem with persistant mount on quorum fail when
                    using SSL
           Product: GlusterFS
           Version: 3.7.13
         Component: core
          Assignee: bugs at gluster.org
          Reporter: klas.mattsson at su.se
                CC: bugs at gluster.org



Created attachment 1180086
  --> https://bugzilla.redhat.com/attachment.cgi?id=1180086&action=edit
Logfile

Description of problem:
When quorum is lost and regained and SSL is used, the clients are unable to
regain working write capabilities.
In some cases, the mount turns stale as well.
mount.glusterfs is being used.

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

How reproducible:
Every time in my lab.

Steps to Reproduce:
1. Create a 3 (uncertain if others are applicable) peer replica with 3 nodes
(arbiter or otherwhise).
2. Activate SSL (self-signed certs with CA file with all client and server pems
on servers and with server pems on clients).
3. Activate quorum.
4: Mount on client.
5: Turn off two nodes.
6: Read only occurs.
7: Start one or two nodes.

Actual results:
The mount is still read-only.

Expected results:
The mount should recover.


Additional info:

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