Bug 1514810
| Summary: | SELinux is preventing snapd from 'write' accesses on the directory /usr/share/bash-completion/completions. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Predrag <predrag.zvijerac> |
| 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: | 27 | CC: | dwalsh, lvrabec, mgrepl, plautrba, pmoore |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:9893e508cd914bf38b65fe7aa8f2fa9b6a4c921691ca264773f7aac1772876fa;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-20 12:36:15 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 1514800 *** |
Description of problem: SELinux is preventing snapd from 'write' accesses on the directory /usr/share/bash-completion/completions. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow snapd to have write access on the completions directory Then you need to change the label on /usr/share/bash-completion/completions Do # semanage fcontext -a -t FILE_TYPE '/usr/share/bash-completion/completions' where FILE_TYPE is one of the following: snappy_home_t, snappy_var_lib_t, snappy_var_run_t, snappy_var_t, systemd_unit_file_t, tmp_t, udev_rules_t, user_home_dir_t. Then execute: restorecon -v '/usr/share/bash-completion/completions' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that snapd should be allowed write access on the completions 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 'snapd' --raw | audit2allow -M my-snapd # semodule -X 300 -i my-snapd.pp Additional Information: Source Context system_u:system_r:snappy_t:s0 Target Context system_u:object_r:usr_t:s0 Target Objects /usr/share/bash-completion/completions [ dir ] Source snapd Source Path snapd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.12-300.fc27.x86_64 #1 SMP Wed Nov 8 16:38:01 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2017-11-16 21:51:40 CET Last Seen 2017-11-16 21:51:40 CET Local ID 0cc24dcf-bb3a-42e3-bbc9-6e3edc630ea5 Raw Audit Messages type=AVC msg=audit(1510865500.520:3373): avc: denied { write } for pid=2316 comm="snapd" name="completions" dev="dm-1" ino=2628542 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir permissive=1 Hash: snapd,snappy_t,usr_t,dir,write Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.13.12-300.fc27.x86_64 type: libreport