Description of problem: Loading a custom SELinux policy module which worked on RHEL 5 gives unhelpful error in RHEL 6. The actual cause was conflict with a file context rule new to RHEL 6. Version-Release number of selected component (if applicable): 2.0.43-4.1.el6 How reproducible: 100% Steps to Reproduce: 1. Create new policy module with file context pattern that already exists in standard policy (e.g. /var/run/passenger(/.*)? ) 2. Try to load it. Actual results: # semodule -i mypolicy.pp /etc/selinux/targeted/contexts/files/file_contexts: Invalid argument libsemanage.semanage_install_active: setfiles returned error code 1. semodule: Failed! Expected results: # semodule -i mypolicy.pp File context already exists for /var/run/passenger: mypolicy.fc line 5 semodule: Failed! or similar message. Additional info: There is a reasonable error message in the Fedora 17 version: # semodule -i mypol.pp /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/run/passenger(/.*)? (system_u:object_r:passenger_var_run_t:s0 and system_u:object_r:var_run_t:s0). /etc/selinux/targeted/contexts/files/file_contexts: Invalid argument libsemanage.semanage_install_active: setfiles returned error code 1. semodule: Failed! Would be nice to include the line number of mypol.fc which caused the error, but at least the Fedora 17 version of the message should be released into RHEL 6.2.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
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. http://rhn.redhat.com/errata/RHBA-2013-0465.html