Description of problem: Problem happened during boot as Domain-0 on Xen hypervisor. SELinux is preventing /usr/bin/touch from 'write' accesses on the file libvirt-guests. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that touch should be allowed write access on the libvirt-guests file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep touch /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:var_lock_t:s0 Target Objects libvirt-guests [ file ] Source touch Source Path /usr/bin/touch Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.17.4-301.fc21.x86_64 #1 SMP Thu Nov 27 19:09:10 UTC 2014 x86_64 x86_64 Alert Count 4 First Seen 2014-12-07 01:28:18 EST Last Seen 2014-12-09 11:37:12 EST Local ID 86967ece-f95d-4d3d-b0f2-7e891f0f4e93 Raw Audit Messages type=AVC msg=audit(1418143032.385:91): avc: denied { write } for pid=802 comm="touch" name="libvirt-guests" dev="tmpfs" ino=20117 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_lock_t:s0 tclass=file permissive=0 type=SYSCALL msg=audit(1418143032.385:91): arch=x86_64 syscall=utimensat success=no exit=EACCES a0=ffffffffffffff9c a1=7fff7d1faf4b a2=0 a3=0 items=0 ppid=795 pid=802 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=touch exe=/usr/bin/touch subj=system_u:system_r:init_t:s0 key=(null) Hash: touch,init_t,var_lock_t,file,write Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 3.17.4-301.fc21.x86_64 type: libreport
Did you disabled the unconfined.pp module?
I do not believe so.
*** Bug 1181308 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.