[Bugs] [Bug 1412240] Glusterd does not reliably start at boot

[bugzilla at redhat.com]

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

Daniel Scime <nybble at thenybble.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nybble at thenybble.com



--- Comment #7 from Daniel Scime <nybble at thenybble.com> ---
I can confirm this same behavior on Gluster 3.9.1 running on Fedora 25. 
Gluster was installed from the dnf repositories.

I have 100% percent reproducibility with this problem.  The steps I have taken
to reproduce the problem are listed below:

1)  Roll two clean Fedora 25 Servers
2)  Generate /etc/hosts files on both servers for name resolution
3)  Install GlusterFS on both hosts using dnf install glusterfs-server
glusterfs-ganesha
4)  Probe Gluster peers
5)  Run gluster volume set all cluster.enable-shared-storage enable
-After waiting a few moments the shared storage location will mount to
/run/gluster/shared_storage
6)  Reboot either node.
7)  Restarted node will have failed to start glusterd.service and shared
storage will not be mounted


The service will start manually once the server has completely restarted but a
mount -a must be run to mount the shared storage.

This is exceptionally problematic as we have attempted to roll an HA cluster
using gluster nfs-ganesha enable.  Since this leverages shared storage starting
in 3.9, restarting a node after enabling the cluster, causes the node to fail
to resume its cluster services.

Manually starting gluster, mounting the volume, and restarting corosync,
pacemaker, etc does not put the node back into production.

This problem cannot be reproduced on CentOS 7 as we have another Gluster 3.8
cluster running on CentOS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=9ybGR3X4Bf&a=cc_unsubscribe