Description of problem: Interrupting a create-live run with CTRL-C, I think. SELinux is preventing /usr/sbin/setfiles from 'read' accesses on the file . ***** Plugin catchall (100. confidence) suggests ************************** If you believe that setfiles should be allowed read access on the 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 restorecon /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 Target Context unconfined_u:object_r:net_conf_t:s0 Target Objects [ file ] Source restorecon Source Path /usr/sbin/setfiles Port <Unknown> Host (removed) Source RPM Packages policycoreutils-2.2.5-4.fc20.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-189.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.16.6-200.fc20.x86_64 #1 SMP Wed Oct 15 13:06:51 UTC 2014 x86_64 x86_64 Alert Count 4 First Seen 2014-10-22 10:01:13 EDT Last Seen 2014-10-22 10:01:14 EDT Local ID 1c7c2ad6-9631-4799-a029-0f601e5c042a Raw Audit Messages type=AVC msg=audit(1413986474.8:787): avc: denied { read } for pid=20858 comm="restorecon" name="config" dev="loop1" ino=39782 scontext=unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:net_conf_t:s0 tclass=file permissive=0 type=SYSCALL msg=audit(1413986474.8:787): arch=x86_64 syscall=open success=no exit=EACCES a0=7fb3d6d1f8a5 a1=0 a2=1b6 a3=240 items=0 ppid=19774 pid=20858 auid=3000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=1 comm=restorecon exe=/usr/sbin/setfiles subj=unconfined_u:system_r:setfiles_t:s0-s0:c0.c1023 key=(null) Hash: restorecon,setfiles_t,net_conf_t,file,read Additional info: reporter: libreport-2.2.3 hashmarkername: setroubleshoot kernel: 3.16.6-200.fc20.x86_64 type: libreport Potential duplicate: bug 923492
*** This bug has been marked as a duplicate of bug 923492 ***