Hide Forgot
Description of problem: Starting a machine with machinectl causes this error. E.g. `machinectl start my-container`. I've seen various other denials occur as well. I eventually set systemd_machined_t to permissive but still get this error. SELinux is preventing systemd-machine from 'getattr' accesses on the file /proc/<pid>/cgroup. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-machine should be allowed getattr access on the cgroup file 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 'systemd-machine' --raw | audit2allow -M my-systemdmachine # semodule -X 300 -i my-systemdmachine.pp Additional Information: Source Context system_u:system_r:systemd_machined_t:s0 Target Context system_u:system_r:unconfined_service_t:s0 Target Objects /proc/<pid>/cgroup [ file ] Source systemd-machine Source Path systemd-machine Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-08 14:16:27 EDT Last Seen 2016-09-08 14:16:27 EDT Local ID d70b1d3a-5dc9-41bc-bcc1-f88260d465fa Raw Audit Messages type=AVC msg=audit(1473358587.691:964): avc: denied { getattr } for pid=34330 comm="systemd-machine" path="/proc/37083/cgroup" dev="proc" ino=733901 scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:system_r:unconfined_service_t:s0 tclass=file permissive=1 Hash: systemd-machine,systemd_machined_t,unconfined_service_t,file,getattr Version-Release number of selected component: selinux-policy-3.13.1-191.14.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.2-201.fc24.x86_64 type: libreport
Here's the denial I get when I set systemd_machined_t to enforcing. SELinux is preventing systemd-machine from write access on the sock_file system_bus_socket. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-machine should be allowed write access on the system_bus_socket sock_file 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 'systemd-machine' --raw | audit2allow -M my-systemdmachine # semodule -X 300 -i my-systemdmachine.pp Additional Information: Source Context system_u:system_r:systemd_machined_t:s0 Target Context system_u:object_r:tmpfs_t:s0 Target Objects system_bus_socket [ sock_file ] Source systemd-machine Source Path systemd-machine Port <Unknown> Host arkham.usersys.redhat.com Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.14.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name arkham.usersys.redhat.com Platform Linux arkham.usersys.redhat.com 4.7.2-201.fc24.x86_64 #1 SMP Fri Aug 26 15:58:40 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-09-08 14:31:02 EDT Last Seen 2016-09-08 14:31:02 EDT Local ID 71500ea1-71fc-4bf7-a676-6d6305ead3be Raw Audit Messages type=AVC msg=audit(1473359462.18:1029): avc: denied { write } for pid=38230 comm="systemd-machine" name="system_bus_socket" dev="tmpfs" ino=860381 scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=sock_file permissive=1 Hash: systemd-machine,systemd_machined_t,tmpfs_t,sock_file,write
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.