Description of problem: network.service after bridge setup described in: http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging network.service fails on start resulting in system without configured network, adding SElinux policy fixes the issue Additional info: libreport version: 2.0.16 kernel: 3.6.2-2.fc18.x86_64 description: :SELinux is preventing /usr/sbin/arping from using the 'setcap' accesses on a process. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that arping should be allowed setcap access on processes labeled netutils_t 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 arping /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context system_u:system_r:netutils_t:s0 :Target Context system_u:system_r:netutils_t:s0 :Target Objects [ process ] :Source arping :Source Path /usr/sbin/arping :Port <Neznámé> :Host (removed) :Source RPM Packages iputils-20121011-1.fc18.x86_64 :Target RPM Packages :Policy RPM selinux-policy-3.11.1-36.fc18.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Enforcing :Host Name (removed) :Platform Linux (removed) 3.6.2-2.fc18.x86_64 #1 SMP Wed Oct : 17 05:56:07 UTC 2012 x86_64 x86_64 :Alert Count 2 :First Seen 2012-10-25 09:49:13 EDT :Last Seen 2012-10-25 10:03:07 EDT :Local ID f03ac9db-2448-4c43-a449-e404f54d863f : :Raw Audit Messages :type=AVC msg=audit(1351173787.182:316): avc: denied { setcap } for pid=2782 comm="arping" scontext=system_u:system_r:netutils_t:s0 tcontext=system_u:system_r:netutils_t:s0 tclass=process : : :type=SYSCALL msg=audit(1351173787.182:316): arch=x86_64 syscall=capset success=no exit=EACCES a0=7f0667b11014 a1=7f0667b1101c a2=7f0667b11010 a3=7fff28777320 items=0 ppid=2764 pid=2782 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=arping exe=/usr/sbin/arping subj=system_u:system_r:netutils_t:s0 key=(null) : :Hash: arping,netutils_t,netutils_t,process,setcap : :audit2allow : :#============= netutils_t ============== :allow netutils_t self:process setcap; : :audit2allow -R : :#============= netutils_t ============== :allow netutils_t self:process setcap; :
Created attachment 633341 [details] File: type
Created attachment 633342 [details] File: hashmarkername
Fixed in selinux-policy-3.11.1-43.fc18.noarch
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.