boltd is causing three selinux alerts: SELinux is preventing boltd from write access on the directory boltd. SELinux is preventing boltd from add_name access on the directory power. SELinux is preventing boltd from create access on the directory power.
Policy RPM selinux-policy-3.14.1-42.fc28.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Raw Audit Messages type=AVC msg=audit(1538505198.882:146): avc: denied { write } for pid=996 comm="boltd" name="boltd" dev="tmpfs" ino=32456 scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1 type=AVC msg=audit(1538505198.882:147): avc: denied { add_name } for pid=996 comm="boltd" name="power" scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1 type=AVC msg=audit(1538505198.882:148): avc: denied { create } for pid=996 comm="boltd" name="power" scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1 Deleting the /var/run/boltd directory and starting the bolt service triggers the alerts.
*** This bug has been marked as a duplicate of bug 1632230 ***