avc: denied { write } for pid=2301 comm="dhclient-script" name="resolv.conf" scontext=root:system_r:dhcpc_t ... tcontext=system_u:object_r:etc_t
restorecon /etc/resolv.conf after install fixes it, however, by that point, you already have a resolv.conf that doesn't have a nameserver in it.
Are you using kickstart and doing anything to modify /etc/resolv.conf during your %post script? Our default install sets the file to system_u:object_r:net_conf_t but gets reset to whatever the parent says if we try touching the file after installation is complete.
Unless "/usr/sbin/authconfig --enablekrb5realmdns --kickstart" touches it, no, I'm not touching it.
Could you check /var/log/anaconda.log for resolv.conf? We log a message for every file we change the context on.
During install? There's nothing in install.log*.
Oh wait, I think this is the box that tracebacked writing the KS file... is the reset to net_conf_t after that?
Setting file contexts is the step right after writing the kickstart config.
OK then. :)