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.
It looks like default installation of Satellite does not clean finished tasks. This makes listing and management of tasks harder. This is a request to setup Satellite in a way that all finished and irrelevant tasks are automatically deleted after a week timeframe.
There are some rake tasks already (Satellite 6.2 only) but these are not run from cron:
[root@tyan-gt24-12 ~]# foreman-rake foreman_tasks:cleanup:config
Global period for cleaning up tasks is not set
The following actions are configured to be deleted automatically after some time:
name delete after
Actions::Foreman::Host::ImportFacts 30d
Actions::Foreman::Puppetclass::Import 30d
These defaults are not sane, no global cleanup period is set so the rake task will actually do not do the job.
Consider using some sane values, it does not make sense to cleanup tasks after ONE YEAR (upstream default), the sane default is one week for global setting and one day for very frequent tasks.
Foreman tasks job is not doing records, if needed the cleanup task can be creating a logfile of all tasks deleted with some information for recording purposes, but database should be clean.
More details at:
https://github.com/theforeman/foreman-tasks#tasks-cleanup
TRIAGE NOTES: This is not big change to do, yet it will increase USER EXPERIENCE. Customers will not need to browse through thousands of pages of finished tasks when resolving tasks errors, listings via CLI will be more usable.
Once this is resolved, please backport this into Satellite 6.1. There are customers stuck at this version.
It is indeed Peter.
Martin I suggest to turn one into 6.1 bug, I think this is very important issue and we have customers in the field with 6.1 instances with database full of old tasks. We need to backport into 6.1 as well. Thanks!
We will not be addressing this bug in the 6.1 code base. If you have concerns with this, please feel free to reach out to me with any concerns or issues you may have. Thank you.