Description of problem: SELinux is preventing systemd-modules from 'getattr' accesses on the file /etc/modprobe.d/kvm.conf. ***** Plugin catchall (100. confidence) suggests ************************** If 您認為 systemd-modules 就預設值應擁有 kvm.conf file 的 getattr 存取權。 Then 您應將此回報為錯誤。 您可產生本機模組，以允許這項存取。 Do allow this access for now by executing: # ausearch -c 'systemd-modules' --raw | audit2allow -M my-systemdmodules # semodule -X 300 -i my-systemdmodules.pp Additional Information: Source Context system_u:system_r:systemd_modules_load_t:s0 Target Context system_u:object_r:modules_conf_t:s0 Target Objects /etc/modprobe.d/kvm.conf [ file ] Source systemd-modules Source Path systemd-modules Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages qemu-common-2.6.0-5.fc24.x86_64 Policy RPM selinux-policy-3.13.1-191.5.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.6.4-301.fc24.x86_64 #1 SMP Tue Jul 12 11:50:00 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-07-26 14:43:01 CST Last Seen 2016-07-26 14:43:01 CST Local ID 35b11f42-d7ee-4d7e-9e13-4bea86deb38d Raw Audit Messages type=AVC msg=audit(1469515381.32:301): avc: denied { getattr } for pid=10647 comm="systemd-modules" path="/etc/modprobe.d/kvm.conf" dev="dm-1" ino=787267 scontext=system_u:system_r:systemd_modules_load_t:s0 tcontext=system_u:object_r:modules_conf_t:s0 tclass=file permissive=0 Hash: systemd-modules,systemd_modules_load_t,modules_conf_t,file,getattr Version-Release number of selected component: selinux-policy-3.13.1-191.5.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.6.4-301.fc24.x86_64 type: libreport
Description of problem: The warning is produced on every boot and lets startup of systemd-modules-load.service fail. Version-Release number of selected component: selinux-policy-3.13.1-191.5.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.6.4-301.fc24.x86_64 type: libreport
Description of problem: The problem appeared after installing VirtualBox x86_64 5.0.26 R1.fc24. Version-Release number of selected component: selinux-policy-3.13.1-191.5.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.6.4-301.fc24.x86_64 type: libreport
Description of problem: Systemd fails to load bbswitch on every boot. I think this happened ever since I upgraded to F24. Version-Release number of selected component: selinux-policy-3.13.1-191.5.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.6.4-301.fc24.x86_64 type: libreport
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.