Description of problem: Repeated complaints from SELinux about chrony access to /run/NetworkManager/no-stub-resolv.conf Version-Release number of selected component (if applicable): 4.2 How reproducible: No action is required. Steps to Reproduce: 1. Install Fedora 35 with Plasma 2. Upgrade to Fedora 36 3. Actual results: Hundreds of alerts like this: time->Sun May 22 07:21:42 2022 type=AVC msg=audit(1653196902.491:1158): avc: denied { getattr } for pid=22082 comm="chronyd" path="/run/NetworkManager/no-stub-resolv.conf" dev="tmpfs" ino=3546 scontext=system_u:system_r:chronyd_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=file permissive=0 Expected results: No alert at all. Additional info: Couldn't reproduce it on a clean install in a VM. At least another daemon shares the same problem, see: time->Sun May 22 07:21:35 2022 type=AVC msg=audit(1653196895.402:1138): avc: denied { read } for pid=25494 comm="unbound-anchor" name="no-stub-resolv.conf" dev="tmpfs" ino=3435 scontext=system_u:system_r:named_t:s0 tcontext=system_u:object_r:NetworkManager_var_run_t:s0 tclass=file permissive=0
*** This bug has been marked as a duplicate of bug 2091275 ***