Gluster's Event Deamon is not allowed by SELINUX

[hunter86bg]

Symptom:

glustereventsd[1312]: Failed to start Eventsd for IPv4: [Errno 13] Permission denied

Event's Daemon Config:

# cat /etc/glusterfs/eventsconfig.json 
{
    "log-level": "INFO",
    "port": 24009,
    "disable-events-log": false
}

AVC Denied:

type=AVC msg=audit(1641684058.017:1042): avc:  denied  { name_bind } for  pid=5949 comm="glustereventsd" src=24009 scontext=system_u:system_r:glusterd_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=udp_socket permissive=0
type=AVC msg=audit(1641684806.621:83): avc:  denied  { name_bind } for  pid=1312 comm="glustereventsd" src=24009 scontext=system_u:system_r:glusterd_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=udp_socket permissive=0
type=USER_MAC_CONFIG_CHANGE msg=audit(1641741688.121:828): pid=149221 uid=0 auid=0 ses=14 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='resrc=port op=add lport=24009 proto=17 tcontext=system_u:object_r:gluster_port_t:s0 comm="semanage" exe="/usr/libexec/platform-python3.6" hostname=? addr=? terminal=? res=success'�UID="root" AUID="root"

Workaround:

# semanage port -a -t gluster_port_t -p udp 24009

Installed package:

# rpm -q glusterfs-selinux
glusterfs-selinux-2.0.1-1.el8.noarch

[hunter86bg]

@Shwetha-Acharya ,
can you guide me into it ?

[Shwetha-Acharya]

@hunter86bg gluster/glusterfs#2091 PR which is part of devel branch should be addressing the issue you are facing.

Which version of glusterfs are you using?

[hunter86bg]

@Shwetha-Acharya ,
oVirt is currently using 8.6 but I believe it will move to v9 with 4.5

[Shwetha-Acharya]

@hunter86bg gluster/glusterfs#2091 is part of glusterfs release 10 (10.0rc0 onwards)
Best we can do is to backport this to release 9 and make this PR available 9.6 onwards

[hunter86bg]

@Shwetha-Acharya ,

thanks that will also work.
As per my understanding glustereventsd config won't be changed on upgrade and oVirt has to do it manually, right ?

[Shwetha-Acharya]

@hunter86bg I have backported gluster/glusterfs#2091 for release 9, once it is merged and 9.6 version is up, that PR will be available.

As per my understanding glustereventsd config won't be changed on upgrade

yes, on upgrade configs should/will not be changing.

We will have to rely on command you suggested as workaround if we want to manually change the custom port. @riteshchikatwar can add more about ovirt.