/etc/resolv.conf wrong SELinux context set when created via vmtoolsd on Red Hat Enterprise Linux 7
Issue
- The
/etc/resolv.confhas been created, but is not populated with the DNS Servers during VMWare guest customization, which obviously causes troubles afterwards. After digging a little deeper, we observed that the/etc/resolv.confhas been created with the wrong SELinux context, which prevents the dhcp daemon to write into this file and hence leaves it untouched. - Wrong SELinux context set for
/etc/resolv.confwhen created via vmtoolsd.
Environment
- Red Hat Enterprise Linux 7
- open-vm-tools
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
