Description of problem: SELinux is preventing systemctl from using the 'setrlimit' accesses on a process. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemctl should be allowed setrlimit access on processes labeled snappy_t 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 'systemctl' --raw | audit2allow -M my-systemctl # semodule -X 300 -i my-systemctl.pp Additional Information: Source Context system_u:system_r:snappy_t:s0 Target Context system_u:system_r:snappy_t:s0 Target Objects Unknown [ process ] Source systemctl Source Path systemctl Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-3.14.7-28.fc34.noarch Local Policy RPM selinux-policy-targeted-3.14.7-28.fc34.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.11.10-xanmod1_cacule.0.fc34 #1 SMP PREEMPT Thu Mar 25 22:01:11 UTC 2021 x86_64 x86_64 Alert Count 1 First Seen 2021-03-29 16:22:28 EDT Last Seen 2021-03-29 16:22:28 EDT Local ID 3871c8f2-0e1d-444c-aee4-b27fa19be5aa Raw Audit Messages type=AVC msg=audit(1617049348.990:2375): avc: denied { setrlimit } for pid=36064 comm="systemctl" scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:system_r:snappy_t:s0 tclass=process permissive=1 Hash: systemctl,snappy_t,snappy_t,process,setrlimit Version-Release number of selected component: selinux-policy-targeted-3.14.7-28.fc34.noarch Additional info: component: selinux-policy reporter: libreport-2.14.0 hashmarkername: setroubleshoot kernel: 5.11.10-xanmod1_cacule.0.fc34 type: libreport Potential duplicate: bug 1912599
Changing the component to snapd for the maintainers to assess.
FEDORA-2022-9d711dbc98 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d711dbc98
FEDORA-2022-59c701f3ef has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-59c701f3ef
FEDORA-2022-9d711dbc98 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-59c701f3ef has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-82bea71e5a has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-82bea71e5a
FEDORA-2022-5df8b52ba4 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5df8b52ba4
FEDORA-2022-82bea71e5a has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-82bea71e5a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-82bea71e5a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5df8b52ba4 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5df8b52ba4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5df8b52ba4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-82bea71e5a has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5df8b52ba4 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.