Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1459686 - logrorate complains on duplicate log entry for /var/log/foreman-proxy/smart_proxy_dynflow_core.log
Summary: logrorate complains on duplicate log entry for /var/log/foreman-proxy/smart_p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Adam Ruzicka
QA Contact: Evgeni Golov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-07 20:03 UTC by Ivan Necas
Modified: 2019-04-01 20:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:05:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19245 0 Normal Closed Smart-proxy logrotates all files in /var/log/foreman-proxy 2020-02-13 23:27:55 UTC
Red Hat Bugzilla 1548098 0 urgent CLOSED After logrotate the smart_proxy_dynflow_core service points to the deleted/orphan log file which results into current lo... 2021-12-10 15:42:37 UTC

Internal Links: 1548098

Description Ivan Necas 2017-06-07 20:03:58 UTC 
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
Comment 1 Ivan Necas 2017-06-07 20:04:55 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/19245 from this bug
Comment 4 Satellite Program 2017-06-07 22:02:46 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19245 has been resolved.
Comment 5 Daniel Lobato Garcia 2017-06-09 13:35:03 UTC 
The commit was cp-ed to rpm/1.15 by Dominic upstream upon PR merge: https://github.com/theforeman/foreman-packaging/commit/06ee68a595da4552e5094cfe0da3859ba81e8ab7
Comment 6 Evgeni Golov 2017-08-30 10:21:55 UTC 
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
Comment 8 Bryan Kearney 2018-02-21 17:05:22 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.