<div dir="ltr"><div dir="ltr"><div>Hi Strahil,</div><div><br></div><div>Selinux policies and rules have to be added for gluster processes to work as intended when selinux is in enforced mode. Could you confirm if you've installed the glusterfs-selinux package in the nodes ?</div><div>If not then you can check out the repo at <a href="https://github.com/gluster/glusterfs-selinux">https://github.com/gluster/glusterfs-selinux</a>.<br></div><div><br></div><div>Regards,</div><div>Srijan<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 6, 2021 at 2:15 AM Strahil Nikolov <<a href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Did anyone receive that e-mail ?<br>
Any hints ?<br>
<br>
Best Regards,<br>
Strahil Nikolov<br>
<br>
В 19:05 +0000 на 30.12.2020 (ср), Strahil Nikolov написа:<br>
> Hello All,<br>
> <br>
> I have been testing Geo Replication on Gluster v 8.3 ontop CentOS<br>
> 8.3.<br>
> It seems that everything works untill SELINUX is added to the<br>
> equasion.<br>
> <br>
> So far I have identified several issues on the Master Volume's nodes:<br>
> - /usr/lib/ld-linux-x86-64.so.2 has a different SELINUX Context than<br>
> the target that it is pointing to. For details check <br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1911133" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1911133</a><br>
> <br>
> - SELINUX prevents /usr/bin/ssh from search access to<br>
> /var/lib/glusterd/geo-replication/secret.pem<br>
> <br>
> - SELinux is preventing /usr/bin/ssh from search access to .ssh<br>
> <br>
> - SELinux is preventing /usr/bin/ssh from search access to<br>
> /tmp/gsyncd-aux-ssh-tnwpw5tx/274d5d142b02f84644d658beaf86edae.sock<br>
> <br>
> Note: Using 'semanage fcontext' doesn't work due to the fact that<br>
> files created are inheriting the SELINUX context of the parent dir<br>
> and you need to restorecon after every file creation by the geo-<br>
> replication process.<br>
> <br>
> - SELinux is preventing /usr/bin/rsync from search access on <br>
> .gfid/00000000-0000-0000-0000-000000000001<br>
> <br>
> Obviously, those needs fixing before anyone is able to use Geo-<br>
> Replication with SELINUX enabled on the "master" volume nodes.<br>
> <br>
> Should I open a bugzilla at <a href="http://bugzilla.redhat.com" rel="noreferrer" target="_blank">bugzilla.redhat.com</a> for the selinux<br>
> policy?<br>
> <br>
> Further details:<br>
> [root@glustera ~]# cat /etc/centos-release<br>
> CentOS Linux release 8.3.2011<br>
> <br>
> [root@glustera ~]# rpm -qa | grep selinux | sort<br>
> libselinux-2.9-4.el8_3.x86_64<br>
> libselinux-utils-2.9-4.el8_3.x86_64<br>
> python3-libselinux-2.9-4.el8_3.x86_64<br>
> rpm-plugin-selinux-4.14.3-4.el8.x86_64<br>
> selinux-policy-3.14.3-54.el8.noarch<br>
> selinux-policy-devel-3.14.3-54.el8.noarch<br>
> selinux-policy-doc-3.14.3-54.el8.noarch<br>
> selinux-policy-targeted-3.14.3-54.el8.noarch<br>
> <br>
> [root@glustera ~]# rpm -qa | grep gluster | sort<br>
> centos-release-gluster8-1.0-1.el8.noarch<br>
> glusterfs-8.3-1.el8.x86_64<br>
> glusterfs-cli-8.3-1.el8.x86_64<br>
> glusterfs-client-xlators-8.3-1.el8.x86_64<br>
> glusterfs-fuse-8.3-1.el8.x86_64<br>
> glusterfs-geo-replication-8.3-1.el8.x86_64<br>
> glusterfs-server-8.3-1.el8.x86_64<br>
> libglusterd0-8.3-1.el8.x86_64<br>
> libglusterfs0-8.3-1.el8.x86_64<br>
> python3-gluster-8.3-1.el8.x86_64<br>
> <br>
> <br>
> [root@glustera ~]# gluster volume info primary<br>
> <br>
> Volume Name: primary<br>
> Type: Distributed-Replicate<br>
> Volume ID: 89903ca4-9817-4c6f-99de-5fb3e6fd10e7<br>
> Status: Started<br>
> Snapshot Count: 0<br>
> Number of Bricks: 5 x 3 = 15<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: glustera:/bricks/brick-a1/brick<br>
> Brick2: glusterb:/bricks/brick-b1/brick<br>
> Brick3: glusterc:/bricks/brick-c1/brick<br>
> Brick4: glustera:/bricks/brick-a2/brick<br>
> Brick5: glusterb:/bricks/brick-b2/brick<br>
> Brick6: glusterc:/bricks/brick-c2/brick<br>
> Brick7: glustera:/bricks/brick-a3/brick<br>
> Brick8: glusterb:/bricks/brick-b3/brick<br>
> Brick9: glusterc:/bricks/brick-c3/brick<br>
> Brick10: glustera:/bricks/brick-a4/brick<br>
> Brick11: glusterb:/bricks/brick-b4/brick<br>
> Brick12: glusterc:/bricks/brick-c4/brick<br>
> Brick13: glustera:/bricks/brick-a5/brick<br>
> Brick14: glusterb:/bricks/brick-b5/brick<br>
> Brick15: glusterc:/bricks/brick-c5/brick<br>
> Options Reconfigured:<br>
> changelog.changelog: on<br>
> geo-replication.ignore-pid-check: on<br>
> geo-replication.indexing: on<br>
> storage.fips-mode-rchecksum: on<br>
> transport.address-family: inet<br>
> nfs.disable: on<br>
> performance.client-io-threads: off<br>
> cluster.enable-shared-storage: enable<br>
> <br>
> I'm attaching the audit log and sealert analysis from glustera (one<br>
> of the 3 nodes consisting of the 'master' volume).<br>
> <br>
> <br>
> Best Regards,<br>
> Strahil Nikolov<br>
> <br>
<br>
-------<br>
<br>
Community Meeting Calendar:<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" rel="noreferrer" target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>
<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div></div>