Bug 2088982 - SELinux complaints after in-place upgrade to Fedora 36
Summary: SELinux complaints after in-place upgrade to Fedora 36
Keywords:
Status: CLOSED DUPLICATE of bug 2091275
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-22 05:51 UTC by Luigi Baldoni
Modified: 2022-09-07 13:49 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-07 13:49:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Luigi Baldoni 2022-05-22 05:51:37 UTC
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

Comment 1 Nikola Knazekova 2022-09-07 13:49:45 UTC

*** This bug has been marked as a duplicate of bug 2091275 ***


Note You need to log in before you can comment on or make changes to this bug.