Hide Forgot
Description of problem: ***** Plugin catchall (100. confidence) suggests *************************** If you believe that iscsid should be allowed read write access on the lock 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 iscsid /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:iscsid_t:s0 Target Context unconfined_u:object_r:var_lock_t:s0 Target Objects lock [ file ] Source iscsid Source Path /sbin/iscsid Port <Unknown> Host jenkins Source RPM Packages iscsi-initiator-utils-6.2.0.872-12.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-39.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name jenkins Platform Linux jenkins 2.6.40.6-0.fc15.i686.PAE #1 SMP Tue Oct 4 00:44:38 UTC 2011 i686 i686 Alert Count 1 First Seen Wed Oct 26 11:18:40 2011 Last Seen Wed Oct 26 11:18:40 2011 Local ID 5697418b-5649-45b6-b9d7-b24c6176eea0 Raw Audit Messages type=AVC msg=audit(1319620720.528:423): avc: denied { read write } for pid=15464 comm="iscsid" name="lock" dev=tmpfs ino=304044 scontext=system_u:system_r:iscsid_t:s0 tcontext=unconfined_u:object_r:var_lock_t:s0 tclass=file type=SYSCALL msg=audit(1319620720.528:423): arch=i386 syscall=open success=no exit=EACCES a0=80923b7 a1=42 a2=1b6 a3=9074740 items=0 ppid=1 pid=15464 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=iscsid exe=/sbin/iscsid subj=system_u:system_r:iscsid_t:s0 key=(null) Hash: iscsid,iscsid_t,var_lock_t,file,read,write audit2allow #============= iscsid_t ============== allow iscsid_t var_lock_t:file { read write }; audit2allow -R #============= iscsid_t ============== allow iscsid_t var_lock_t:file { read write }; Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. service iscsid start 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 749136 ***