[Bugs] [Bug 1463641] [Ganesha] Ganesha service failed to start on new node added in existing ganeshacluster

[bugzilla at redhat.com]

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

Kaleb KEITHLEY <kkeithle at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |Triaged
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |kkeithle at redhat.com



--- Comment #1 from Kaleb KEITHLEY <kkeithle at redhat.com> ---
Looking at all the various selinux-policy packages in RHEL and Fedora, there
are policies for glusterd and nfs-ganesha in selinux-policy for RHEL7.3.z,
RHEL7.4, and Fedora 26 and 27.

Since they're not in Fedora 25 (and before I saw that they're in F26 and F27) I
was tempted lift the policy bits from RHEL7 and add -selinux subpackages to
gluster and nfs-ganesha. I'm not sure that's a good idea though at this point.

In the mean time it appears that all I need to do is add either
  semanage boolean -m ganesha_use_fusefs --on
or the
  %selinux_{set,unset}_booleans
to %post ganesha and %postun ganesha in the glusterfs.spec.

for Fedora 26 and later. Until {RHEL,CentOS} 7.4 ships this can't be added for
RHEL as rpm packaging is not able to discriminate between there are no CentOS
Z-Stream releases and rpm packages don't distinguish between 7.3 and 7.4

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