Bug 1636660
| Summary: | SELinux is preventing (boltd) from 'mounton' accesses on the directory /run/systemd/unit-root/run/boltd. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> |
| Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dwalsh, lvrabec, mgrepl, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:46c911a8f05007638070614ecc17550bcbe29514973df28a3804c57867f20f5d;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-12 16:08:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** This bug has been marked as a duplicate of bug 1636823 *** |
Description of problem: SELinux is preventing (boltd) from 'mounton' accesses on the directory /run/systemd/unit-root/run/boltd. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /run/systemd/unit-root/run/boltd default label should be init_var_run_t. Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly. Do # /sbin/restorecon -v /run/systemd/unit-root/run/boltd ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that (boltd) should be allowed mounton access on the boltd directory 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 '(boltd)' --raw | audit2allow -M my-boltd # semodule -X 300 -i my-boltd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:boltd_var_run_t:s0 Target Objects /run/systemd/unit-root/run/boltd [ dir ] Source (boltd) Source Path (boltd) Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.3-5.fc30.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.19.0-0.rc6.git3.1.fc30.x86_64 #1 SMP Thu Oct 4 14:38:21 UTC 2018 x86_64 x86_64 Alert Count 1 First Seen 2018-10-06 15:58:44 +05 Last Seen 2018-10-06 15:58:44 +05 Local ID 15e427ed-28bd-44e9-8ad1-3bedafa2d593 Raw Audit Messages type=AVC msg=audit(1538823524.22:239): avc: denied { mounton } for pid=2659 comm="(boltd)" path="/run/systemd/unit-root/run/boltd" dev="tmpfs" ino=50740 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:boltd_var_run_t:s0 tclass=dir permissive=0 Hash: (boltd),init_t,boltd_var_run_t,dir,mounton Version-Release number of selected component: selinux-policy-3.14.3-5.fc30.noarch Additional info: component: selinux-policy reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.19.0-0.rc6.git3.1.fc30.x86_64 type: libreport