Bug 472419 - SELinux error messages on RHEL5 upon install
SELinux error messages on RHEL5 upon install
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
All Linux
high Severity high
: 1.1
: ---
Assigned To: Matthew Farrellee
Kim van der Riet
Depends On:
  Show dependency treegraph
Reported: 2008-11-20 13:05 EST by Robert Rati
Modified: 2009-02-04 11:04 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-04 11:04:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Rati 2008-11-20 13:05:52 EST
Description of problem:
When installing condor on a RHEL5 system with SELinux disabled, I see the following error messages:

libsepol.context_from_record: MLS is enabled, but no MLS context found
libsepol.context_from_record: could not create context structure
libsemanage.validate_handler: invalid context system_u:object_r:unconfined_execmem_exec_t specified for /usr/sbin/condor_startd [all files]
libsemanage.dbase_llist_iterate: could not iterate over records
/usr/sbin/semanage: Could not add file context for /usr/sbin/condor_startd

We should be able to install on a system without SELinux and not get errors.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Matthew Farrellee 2008-11-20 13:13:19 EST
This is probably as simple as checking getenforce before issuing SELinux commands. However, if SELinux is later enabled it could be a problem.
Comment 2 Matthew Farrellee 2008-11-20 16:20:12 EST
Only setup SELinux context if SELinux is enabled

Fixed in 7.2.0-0.3
Comment 5 errata-xmlrpc 2009-02-04 11:04:35 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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