Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
In Fedora we have this rule for mysql directories:
/var/lib/mysql(-files|-keyring)?(/.*)? mysqld_db_t
In RHEL we only have:
/var/lib/mysql(/.*)? mysqld_db_t
For RHSCL packages (rh-mysql56 specifically) we now started to use /var/opt/rh/rh-mysql56/lib/mysql-files (because of bz #1384962) and we also define this rule:
/var/opt/rh/rh-mysql56 = /var (using semanage fcontext -a -e ...)
Since selinux's "equality" cannot be defined twice for given directory, we cannot define something like the following in mysql packge:
/var/lib/mysql = /var/lib/mysql-files
or something like
/var/opt/rh/rh-mysql56/lib/mysql-files = /var/lib/mysql
So I think we should change the definition in selinux-policy to be the same as in Fedora:
/var/lib/mysql(-files|-keyring)?(/.*)? mysqld_db_t
This would help in all packages we ship, so it wouldn't require us to fix particular packages.
Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-102.el7.noarch
Steps to Reproduce:
1. ls -lZd /var/opt/rh/rh-mysql56/lib/mysql-files
Actual results:
drwxr-x---. mysql mysql system_u:object_r:var_lib_t:s0 /var/opt/rh/rh-mysql56/lib/mysql-files/
Expected results:
drwxr-x---. mysql mysql system_u:object_r:mysqld_db_t:s0 /var/opt/rh/rh-mysql56/lib/mysql-files/
To correspond the conflict, this is what I see when trying to define it specifically for one directory:
#> semanage fcontext -a -e /var/lib/mysql /var/opt/rh/rh-mysql56/lib/mysql-files
ValueError: File spec /var/opt/rh/rh-mysql56/lib/mysql-files conflicts with equivalency rule '/var/opt/rh/rh-mysql56 /var'; Try adding '/var/lib/mysql-files' instead
Based on the results of our automated TC, this bug is fixed in 3.13.1-124.el7. Not switching to VERIFIED right now, because the bug needs to be added to the selinux-policy errata first.
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-2017:1861