Bug 1729001
| Summary: | SELinux is preventing snapd from 'write' accesses on the directory snap.rambox. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | a.wellbrock |
| Component: | snapd | Assignee: | Zygmunt Krynicki <me> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | dwalsh, go-sig, lvrabec, me, mgrepl, ngompa13, plautrba, zpytela |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:7f2d4bf839d52d6f33f1bfef3279fb05f26df864241396dd5d3a783a57ccd041;VARIANT_ID=workstation; | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-18 11:51: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: | |||
Description of problem: This problem happens on Fedora 30, latest kernel, when I use the Gnome Store to remove the Snap-Package of Rambox. I removed it, since the package seems not to work at all, at least I'm not able to start it, so I'm suspecting SELinux to be the culprit. A friend with who installed Fedora 30 from scratch does not appear to have this problem. Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.15-300.fc30.x86_64 type: libreport This bug is now tracked in an aggregate helper issue: https://bugs.launchpad.net/snapd/+bug/1863747 |
Description of problem: This problem happens on Fedora 30, latest kernel, when I use the Gnome Store to remove the Snap-Package of Rambox. I removed it, since the package seems not to work at all, at least I'm not able to start it, so I'm suspecting SELinux to be the culprit. A friend with who installed Fedora 30 from scratch does not appear to have this problem. SELinux is preventing snapd from 'write' accesses on the directory snap.rambox. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that snapd should be allowed write access on the snap.rambox 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 unconfined_u:object_r:user_tmp_t:s0 Target Objects snap.rambox [ dir ] Source snapd Source Path snapd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.3-39.fc30.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.1.15-300.fc30.x86_64 #1 SMP Tue Jun 25 14:07:22 UTC 2019 x86_64 x86_64 Alert Count 1 First Seen 2019-07-10 09:53:46 CEST Last Seen 2019-07-10 09:53:46 CEST Local ID 161f960a-f80f-47b7-8596-59e7a08b6060 Raw Audit Messages type=AVC msg=audit(1562745226.786:1600): avc: denied { write } for pid=4387 comm="snapd" name="snap.rambox" dev="tmpfs" ino=895840 scontext=system_u:system_r:snappy_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=dir permissive=1 Hash: snapd,snappy_t,user_tmp_t,dir,write Version-Release number of selected component: selinux-policy-3.14.3-39.fc30.noarch Additional info: component: selinux-policy reporter: libreport-2.10.0 hashmarkername: setroubleshoot kernel: 5.1.15-300.fc30.x86_64 type: libreport Potential duplicate: bug 1628356