Is the glusterfs daemonset very specific to RHEL/CentOS ? My K8S cluster is setup on Debian machines and when I spin up a vanilla daemonset for glusterfs, I encounter many issues. Like :
[2018-11-09 11:45:45.672506] E [MSGID: 106244] [glusterd.c:1764:init] 0-management: creation of 1 listeners failed, continuing with succeeded transport
[2018-11-09 11:45:47.200774] E [MSGID: 101032] [store.c:441:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info. [No such file or directory]
[2018-11-09 11:45:47.200866] E [MSGID: 101032] [store.c:441:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info. [No such file or directory]
And
[2018-11-09 11:59:19.909406] E [socket.c:802:__socket_server_bind] 0-socket.management: binding to failed: Address already in use
[2018-11-09 11:59:19.909429] E [socket.c:805:__socket_server_bind] 0-socket.management: Port is already in use
The glusterd service fails to load inside the Pod.
Is the glusterfs daemonset very specific to RHEL/CentOS ? My K8S cluster is setup on Debian machines and when I spin up a vanilla daemonset for glusterfs, I encounter many issues. Like :
And
The
glusterdservice fails to load inside the Pod.