Bug 1825177 - Set relevant selinux booleans to "on" state to allow rsync operation for gluster
Summary: Set relevant selinux booleans to "on" state to allow rsync operation for gluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: selinux
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 2
Assignee: Sunny Kumar
QA Contact: Arun Kumar
URL:
Whiteboard:
Depends On:
Blocks: 1813917
TreeView+ depends on / blocked
 
Reported: 2020-04-17 10:11 UTC by Arun Kumar
Modified: 2020-06-21 17:41 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.0-34
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-16 06:19:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2572 0 None None None 2020-06-16 06:19:56 UTC

Description Arun Kumar 2020-04-17 10:11:21 UTC
Description of problem:

Boolean option  "rsync_client" and "rsync_full_access" should be set to "on" to fix the rsync permission issue referred in the link[1]. 
Setting these boolean values to "on "fixes the problem of file permissions mentioned in the bug[2]

These options should be persistently set to "on" state 
to fix the problem of rsync operation not working with gluster rpm  

Solution:
--------------
# setsebool -P  rsync_full_access on
# setsebool -P rsync_client on

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1824842#c8

[2]:  https://bugzilla.redhat.com/show_bug.cgi?id=1821759#c5

Comment 3 Sunny Kumar 2020-04-20 12:05:17 UTC
Upstream patch:
https://review.gluster.org/#/c/glusterfs/+/24348/.

Comment 23 errata-xmlrpc 2020-06-16 06:19:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2572


Note You need to log in before you can comment on or make changes to this bug.