RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When resuming from suspend NetworkManager is writing out /etc/resolv.conf.tmp which is being created as etc_t this is then being moved to replace the existing /etc/resolv.conf

This is I think the related create...

type=AVC msg=audit(1285868806.229:1625): avc:  granted  { create } for  pid=28423 comm="NetworkManager" name="resolv.conf.tmp" scontext=system_u:system_r:devicekit_power_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=file

It's then failing to unlink the resolv.conf it created, when I try to reconnect leaving DNS config in a wonky state.

Version-Release number of selected component (if applicable):

[mchappel@mchappel ~]$ rpm -q selinux-policy
selinux-policy-3.7.19-54.el6.noarch

How reproducible:

Every time

Steps to Reproduce:
1. Connect to network using NetworkManager
2. Suspend machine
3. Restart machine
  
Actual results:

/etc/resolv.conf and /etc/hosts have a context of system_u:object_r:etc_t:s0

Expected results:

/etc/resolv.conf and /etc/hosts have a context of system_u:object_r:net_conf_t:s0

Miroslav add


optional_policy(`
	networkmanager_domtrans(devicekit_power_t)
')

Fixed in selinux-policy-3.7.19-56.el6.noarch

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
With SELinux running in the enforcing mode, resuming the system from the Suspend mode failed, because the /etc/resolv.conf file did not have the correct security context. This was caused by NetworkManager, which was running under wrong SELinux domain, "devicekit_power_t". With this update, the proper SELinux domain transition from DeviceKit-power to NetworkManager has been added, and resuming from the Suspend mode now works as expected.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0526.html