Description of problem: The following error message is output at the start of the boot sequence: SELinux: permission module_request in class system not found in policy, bad pol icy SELinux: the definition of a class is incorrect Version-Release number of selected component (if applicable): selinux-policy-targeted-3.6.32-6.fc12.noarch libselinux-debuginfo-2.0.86-2.fc12.i686 libselinux-devel-2.0.86-2.fc12.i686 libselinux-2.0.86-2.fc12.i686 libselinux-python-2.0.86-2.fc12.i686 selinux-policy-3.6.32-6.fc12.noarch libselinux-utils-2.0.86-2.fc12.i686 How reproducible: Always Steps to Reproduce: 1. Boot the system 2. 3. Actual results: Messages above output Expected results: No error messages Additional info:
Please complete the full yum -y upgrade to get to the latest policy and latest tools.
I have done a yum upgrade and selinux-policy and selinux-policy-targeted were upgraded to 3.6.32-7.fc12, and I still get the error messages. The libselinux packages appear to be up to date already. I subsequently upgraded the two packages to 3.6.32-8.fc12 and the error messages still occur. I noticed that during the yum upgrade, I get the following error message: Updating : selinux-policy-targeted-3.6.32-8.fc12.noarch 2/4 libsepol.permission_copy_callback: Module BackupPC depends on permission request_module in class system, not satisfied (No such file or directory). libsemanage.semanage_link_sandbox: Link packages failed (No such file or directory). semodule: Failed! I'm not clear if this is pertinent, or what I need to do to resolve it.
Same here, this seems related to bug #524113. I'll try removing BackupPC and see if relabeling works.
Yes we need an updated BackupPC package to rebuild the policy. We accidently build a selinux-policy with a named access request_module instead of module_request. So for now remove the BackupPC module package. semodule -r BackupPC Then perform the selinux-policy-upgrade All BackupPC has do to is rebuild against the latest selinux-policy package and we should be back in sync. This is a bug in selinux-policy that caused BackupPC to suck in the wrong access type. Sorry.
BackupPC has just been rebuilt (BackupPC-3_1_0-8_fc12).