Description of problem: While booting a Fedora 25 system we see these messages: Sep 09 14:03:15 localhost.localdomain systemd[1]: Unable to fix SELinux security context of /run/systemd/inaccessible/blk: Permission denied Sep 09 14:03:15 localhost.localdomain audit[1]: AVC avc: denied { getattr } for pid=1 comm="systemd" path="/run/systemd/inaccessible/blk" dev="tmpfs" ino=9065 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=blk_file permissive=0 Sep 09 14:03:15 localhost.localdomain audit[1]: AVC avc: denied { getattr } for pid=1 comm="systemd" path="/run/systemd/inaccessible/blk" dev="tmpfs" ino=9065 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=blk_file permissive=0 Sep 09 14:03:17 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=blk-availability comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 09 14:03:17 localhost.localdomain audit[1]: AVC avc: denied { getattr } for pid=1 comm="systemd" path="/run/systemd/inaccessible/blk" dev="tmpfs" ino=9065 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=blk_file permissive=0 Sep 09 14:03:17 localhost.localdomain systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Version-Release number of selected component (if applicable): systemd-231-4.fc25.x86_64 selinux-policy-3.13.1-211.fc25.noarch How reproducible: This happens during the Cockpit integration tests, for most test runs on Fedora 25. Just booting the system is usually enough to make it happen. Example: https://stefw.fedorapeople.org/logs/pull-ba275a3a-verify-fedora-25/TestSession-testBasic-10.111.113.252-FAIL.log
Also happens with Fedora 25 Workstation, 20160909.n.0 nightly build. SELinux is preventing systemd from getattr access on the blk_file /run/systemd/inaccessible/blk. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /run/systemd/inaccessible/blk default label should be init_var_run_t. Then you can run restorecon. Do # /sbin/restorecon -v /run/systemd/inaccessible/blk ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that systemd should be allowed getattr access on the blk blk_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: # ausearch -c 'systemd' --raw | audit2allow -M my-systemd # semodule -X 300 -i my-systemd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:tmpfs_t:s0 Target Objects /run/systemd/inaccessible/blk [ blk_file ] Source systemd Source Path systemd Port <Unknown> Host localhost Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-208.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name localhost.localdomain Platform Linux localhost.localdomain 4.8.0-0.rc4.git0.1.fc25.x86_64 #1 SMP Mon Aug 29 19:28:01 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-10 00:30:29 EDT Last Seen 2016-09-10 00:30:29 EDT Local ID 6d22634d-71e9-4374-b03a-59ae36a51c49 Raw Audit Messages type=AVC msg=audit(1473481829.783:107): avc: denied { getattr } for pid=1 comm="systemd" path="/run/systemd/inaccessible/blk" dev="tmpfs" ino=1191 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=blk_file permissive=0 Hash: systemd,init_t,tmpfs_t,blk_file,getattr
Is this a duplicate of 1367280?
*** This bug has been marked as a duplicate of bug 1367280 ***