Description of problem: With remote execution installed with foreman 1.15, the logrotate complains about duplicate recoreds /etc/cron.daily/logrotate: error: tfm-rubygem-smart_proxy_dynflow_core:1 duplicate log entry for /var/log/foreman-proxy/smart_proxy_dynflow_core.log Version-Release number of selected component (if applicable): foreman-proxy-1.15.0-1.el7.noarch tfm-rubygem-smart_proxy_dynflow_core-0.1.6-2.fm1_15.el7.noarch How reproducible: daily Steps to Reproduce: 1. logrotate /etc/logrotate.conf Actual results: error message is produced Expected results: no error messages Additional info: this also spams /var/spool/mail/root, that should be kept clean for taking attention to real potential issues: actually noticed this while looking reviewing check for unread root messages in https://github.com/iNecas/foreman_maintain/pull/56/files
Connecting redmine issue http://projects.theforeman.org/issues/19245 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19245 has been resolved.
The commit was cp-ed to rpm/1.15 by Dominic upstream upon PR merge: https://github.com/theforeman/foreman-packaging/commit/06ee68a595da4552e5094cfe0da3859ba81e8ab7
FAILED_QA Version tested: Satellite 6.3 Snap 13 foreman-proxy-1.15.3-1.el7sat.noarch tfm-rubygem-smart_proxy_dynflow_core-0.1.6-2.fm1_15.el7sat.noarch [root@sat63-qa-rhel7 ~]# sh /etc/cron.daily/logrotate error: tfm-rubygem-smart_proxy_dynflow_core:1 duplicate log entry for /var/log/foreman-proxy/smart_proxy_dynflow_core.log Seems one half of the upstream commits did not make it downstream: # grep -r /var/log/foreman-proxy /etc/logrotate.d/ /etc/logrotate.d/foreman-proxy:/var/log/foreman-proxy/*log { /etc/logrotate.d/tfm-rubygem-smart_proxy_dynflow_core:/var/log/foreman-proxy/smart_proxy_dynflow_core.log { https://github.com/theforeman/foreman-packaging/commit/06ee68a595da4552e5094cfe0da3859ba81e8ab7 is there https://github.com/theforeman/foreman-packaging/pull/1610/files is not
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336