Description of problem: When I run restorecon on /etc, it founds /etc/syslog.conf have incorrect SELinux context. Also that better way for rsyslog would be to use /etc/rsyslog.d for such a cases. Version-Release number of selected component (if applicable): beaker-distribution-install-1.10-14.noarch selinux-policy-targeted-3.10.0-96.fc16.noarch How reproducible: always Steps to Reproduce: 1. restorecon -vR /etc/ Actual results: # restorecon -vR /etc/ restorecon reset /etc/syslog.conf context unconfined_u:object_r:etc_t:s0->unconfined_u:object_r:syslog_conf_t:s0 Expected results: No problem should be reported Additional info: http://git.fedorahosted.org/cgit/beaker.git/tree/Tasks/distribution/install/default/runtest.sh#n78
It looks like that syslog.conf stuff has no effect on RHEL6+ (which uses rsyslog instead), and it seems quite questionable. I doubt anything else is even still relying on that redirection of local2, seems like an RHTS-ism. The task should just append to /etc/syslog.conf only if it already exists. That way the hack will continue to happen on RHEL5 and lower where it actually has some effect, but won't create spurious files for no reason on newer distros.
On Gerrit: http://gerrit.beaker-project.org/2755
distribution-install-1.12-1 has been released.