Bug 295881 - Error messages when updating selinux-policy-targeted
Error messages when updating selinux-policy-targeted
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-19 03:06 EDT by David Juran
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version: selinux-policy-targeted-2.4.6-94.fc6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-08 12:07:27 EDT
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 David Juran 2007-09-19 03:06:02 EDT
Description of problem:
When running yum upgrade this morning I got the following error messages:

Updating  : selinux-policy-targeted      ####################### [ 7/16] 

libsepol.context_from_record: type httpd_nagios_script_exec_t is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert
system_u:object_r:httpd_nagios_script_exec_t:s0 to sid
/etc/selinux/targeted/contexts/files/file_contexts:  line 270 has invalid
context system_u:object_r:httpd_nagios_script_exec_t:s0
libsemanage.semanage_install_active: setfiles returned error code 1.
semodule:  Failed!

Version-Release number of selected component (if applicable):
Comment 1 Alexei Podtelezhnikov 2007-09-19 22:18:17 EDT
Yeah... This is a very BAD update
Well, instead of updating I removed selinux-policy, installed 2.4.6-88.fc6, 
and enforced it. The thing prevents file system checks now :)))
So I had to boot with selinux=0.  
Comment 2 Daniel Walsh 2007-09-22 08:04:17 EDT
What do you mean?  You can always boot with enforcing=0, which will maintain
your file labeleing?  What AVC messages are you seeing that is preventing "file
system checks"?
SELinux releases on released OS, never add additional lock down (Or at least
thats the goal).  But sometimes an update of other parts of the system could
trigger other SELinux errors, like an update to the kernel.


Should be showing up in testing.
Comment 3 David Juran 2007-10-08 12:07:27 EDT
And in updates now. Thanks (-:

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