I noticed this error during "yum update" (which is of course actually dnr, since this is F22): Upgrading : pcre-8.37-5.fc22.x86_64 5/444 libsepol.permission_copy_callback: Module hello depends on permission kill in class service, not satisfied (No such file or directory). libsemanage.semanage_link_sandbox: Link packages failed (No such file or directory). semodule: Failed! I don't have any idea if this is really a problem, but thought I should report it.
Thank you for the report. pcre package does deliver any SELinux policy. Although pcre implements JIT, so it requires executable and writable memory pages in some cases and pcre applications may need SELinux policy tuned for that, this pcre-8.37-5.fc22.x86_64 update did not bring any changes in the JIT. Therefore I reassign this issue to SELinux policy component because I cannot see any problem in the pcre.
Laine, the problem is with hello.pp policy module. Is this your local policy module?
Where would it be located? If I've created any local policy module, it was at sometime in the far past and following instructions from someone else...
# semodule -l |grep hello
Hmm, I get... Upgrading : pcre-8.38-4.fc23.i686 41/82 libsemanage.semanage_load_files: Failed to read file /var/lib/selinux/targeted/tmp/modules/400/mypol/cil. (No such file or directory). semodule: Failed! I didn't get this on any other package update, although surely some other ones must trigger libsemanage. It might be because: - pcre was upgraded last, and libsemanage acts in bulk, OR - pcre executes ldconfig. I have added 'mypol' a number of times to fix policy problems during F22 beta and F23 beta. For some reason /var/lib/selinux/targeted/active/modules/400/mypol/cil is an empty file, which I assume is triggering this.
Could you try to run # semodule -B
The machine in question was upgraded to F23 a month ago, and I *think* I may have found the "hello.pp" module and deleted it based on your advice but then forgot to report about it. I did run "semodule -B" just now, and it exited with no output, but I'm guessing that would only be relevant if there was some way for me to retriggerthe pcre update that caused the problem in the first place. Assuming that I found a hello module and deleted, I'm okay closing this as NOTABUG it you are. On the other hand if there's something I can try with the machine in its new state, let me know.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.