Description of problem: sudo service NetworkManager restart SELinux is preventing /usr/bin/python3.4 from 'connectto' accesses on the unix_stream_socket /run/NetworkManager/private. ***** Plugin catchall_boolean (89.3 confidence) suggests ****************** If you want to enable cluster mode for daemons. Then you must tell SELinux about this by enabling the 'daemons_enable_cluster_mode' boolean. You can read 'NetworkManager_selinux' man page for more details. Do setsebool -P daemons_enable_cluster_mode 1 ***** Plugin catchall (11.6 confidence) suggests ************************** If you believe that python3.4 should be allowed connectto access on the private unix_stream_socket 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: # grep dnssec-trigger- /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:dnssec_trigger_t:s0 Target Context system_u:system_r:NetworkManager_t:s0 Target Objects /run/NetworkManager/private [ unix_stream_socket ] Source dnssec-trigger- Source Path /usr/bin/python3.4 Port <Unknown> Host (removed) Source RPM Packages python3-3.4.1-16.fc21.x86_64 Target RPM Packages Policy RPM selinux-policy-3.13.1-105.19.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.0.8-200.fc21.x86_64 #1 SMP Fri Jul 10 21:09:54 UTC 2015 x86_64 x86_64 Alert Count 2 First Seen 2015-08-03 16:04:07 CEST Last Seen 2015-08-03 16:04:21 CEST Local ID a3e2c6a8-f4dd-4c9b-9f87-287da1c2c016 Raw Audit Messages type=AVC msg=audit(1438610661.732:131463): avc: denied { connectto } for pid=25980 comm="dnssec-trigger-" path="/run/NetworkManager/private" scontext=system_u:system_r:dnssec_trigger_t:s0 tcontext=system_u:system_r:NetworkManager_t:s0 tclass=unix_stream_socket permissive=1 type=SYSCALL msg=audit(1438610661.732:131463): arch=x86_64 syscall=connect success=yes exit=0 a0=5 a1=7ffd0bf7f870 a2=21 a3=0 items=0 ppid=24494 pid=25980 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=dnssec-trigger- exe=/usr/bin/python3.4 subj=system_u:system_r:dnssec_trigger_t:s0 key=(null) Hash: dnssec-trigger-,dnssec_trigger_t,NetworkManager_t,unix_stream_socket,connectto Version-Release number of selected component: selinux-policy-3.13.1-105.19.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 4.0.8-200.fc21.x86_64 type: libreport
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.