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:
* if the fcontext pattern is defined in policy then adding the same pattern should always result in an error message
* if the fcontext pattern is defined in policy and cannot be deleted then every attempt to remove such fcontext pattern should result in an error message
Version-Release number of selected component (if applicable):
policycoreutils-python-2.0.83-30.1.el6_8.x86_64
policycoreutils-2.0.83-30.1.el6_8.x86_64
How reproducible:
* always
Steps to Reproduce:
# semanage fcontext -l | grep /var/log/httpd
/var/log/httpd(/.*)? all files system_u:object_r:httpd_log_t:s0
# semanage fcontext -a -t httpd_log_t '/var/log/httpd(/.*)?'
libsemanage.dbase_llist_query: could not query record value (No such file or directory).
# semanage fcontext -a -t httpd_log_t '/var/log/httpd(/.*)?'
# semanage fcontext -a -t httpd_log_t '/var/log/httpd(/.*)?'
# semanage fcontext -l | grep /var/log/httpd
/var/log/httpd(/.*)? all files system_u:object_r:httpd_log_t:s0
# semanage fcontext -d -t httpd_log_t '/var/log/httpd(/.*)?'
# semanage fcontext -d -t httpd_log_t '/var/log/httpd(/.*)?'
/usr/sbin/semanage: File context for /var/log/httpd(/.*)? is defined in policy, cannot be deleted
# semanage fcontext -d -t httpd_log_t '/var/log/httpd(/.*)?'
/usr/sbin/semanage: File context for /var/log/httpd(/.*)? is defined in policy, cannot be deleted
#
Red Hat Enterprise Linux version 6 is in the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.
This issue is fixed in Red Hat Enterprise Linux version 7.