Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
foreman-maintain tool can easily generate a lot of logs (i.e. when used as a services check tool every few minutes). Default Satellite deployment should housekeep those logs automatically, similarly like e.g. /var/log/foreman or /var/log/foreman-proxy .
Please provide in part of foreman-maintain package a file like (copy from foreman logs):
# cat /etc/logrotate.d/foreman-maintain
# Foreman-maintain logs:
/var/log/foreman-maintain/*.log {
daily
missingok
rotate 14
compress
delaycompress
notifempty
copytruncate
}
#
Version-Release number of selected component (if applicable):
Sat6.9
How reproducible:
100%
Steps to Reproduce:
1. Repeatedly run "foreman-maintain service status" or any other f-m command
2. Check that the /var/log/foreman-maintain/foreman-maintain.log* logs are never logrotated / housekept.
Actual results:
2. No logrotation.
Expected results:
2. Some reasonable logrotation (not necessarily the one I suggested).
Additional info:
Verified.
Tested on Satellite 6.10.0 Snap 16.0
Version: rubygem-foreman_maintain-0.8.13-2.el7sat.noarch
Steps:
1. # rpm -qc rubygem-foreman_maintain
2. # cat /etc/logrotate.d/foreman_maintain
3. # ll -h /var/log/foreman-maintain/
Observation:
Logs under /var/log/foreman-maintain/*.log are being rotated `daily` and has same logrotate config as /var/log/foreman and /var/log/foreman-tasks.
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 (Satellite 6.10 Satellite Maintenance Release), 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/RHBA-2021:4697
Description of problem: foreman-maintain tool can easily generate a lot of logs (i.e. when used as a services check tool every few minutes). Default Satellite deployment should housekeep those logs automatically, similarly like e.g. /var/log/foreman or /var/log/foreman-proxy . Please provide in part of foreman-maintain package a file like (copy from foreman logs): # cat /etc/logrotate.d/foreman-maintain # Foreman-maintain logs: /var/log/foreman-maintain/*.log { daily missingok rotate 14 compress delaycompress notifempty copytruncate } # Version-Release number of selected component (if applicable): Sat6.9 How reproducible: 100% Steps to Reproduce: 1. Repeatedly run "foreman-maintain service status" or any other f-m command 2. Check that the /var/log/foreman-maintain/foreman-maintain.log* logs are never logrotated / housekept. Actual results: 2. No logrotation. Expected results: 2. Some reasonable logrotation (not necessarily the one I suggested). Additional info: