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.
DescriptionSteffen Froemer
2019-06-24 09:13:31 UTC
Description of problem:
Docs of foreman_tasks:cleanup contain wrong information
Version-Release number of selected component (if applicable):
tfm-rubygem-foreman-tasks-0.14.4.6-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. foreman-rake -D foreman_tasks:cleanup
Actual results:
rake foreman_tasks:cleanup:config
Show the current configuration for auto-cleanup
rake foreman_tasks:cleanup:run
Clean tasks based on filter and age. ENV variables:
* TASK_SEARCH : scoped search filter (example: 'label = "Actions::Foreman::Host::ImportFacts"')
* AFTER : delete tasks created after *AFTER* period. Expected format is a number followed by the time unit (s,h,m,y), such as '10d' for 10 days
* STATES : comma separated list of task states to touch with the cleanup, by default only stopped tasks are covered, special value all can be used to clean the tasks, disregarding their states
* NOOP : set to "true" if the task should not actually perform the deletion
* VERBOSE : set to "true" for more verbose output
* BATCH_SIZE : the size of batches the tasks get processed in (1000 by default)
* TASK_BACKUP : set to "true" or "false" to enable/disable task backup
If none of TASK_SEARCH, BEFORE, STATES is specified, the tasks will be cleaned based
configuration in settings
Expected results:
There should no reference shown regarding 'BEFORE' statement, as it seems this is deprecated [1]. In addition, there should be an information, that the time-value of 'started_at' will be referenced.
Also it's not really clear, how the AFTER keyword is working.
What are the time units (s,h,m,y), when directly afterwards we talk about 'd'? If this is just an example list, it should be declared as such (like (e.g. s = seconds, h = hours, d = days, ...)
Additional info:
[1]: https://projects.theforeman.org/issues/8144
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 (Important: Satellite 6.8 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/RHSA-2020:4366
Description of problem: Docs of foreman_tasks:cleanup contain wrong information Version-Release number of selected component (if applicable): tfm-rubygem-foreman-tasks-0.14.4.6-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. foreman-rake -D foreman_tasks:cleanup Actual results: rake foreman_tasks:cleanup:config Show the current configuration for auto-cleanup rake foreman_tasks:cleanup:run Clean tasks based on filter and age. ENV variables: * TASK_SEARCH : scoped search filter (example: 'label = "Actions::Foreman::Host::ImportFacts"') * AFTER : delete tasks created after *AFTER* period. Expected format is a number followed by the time unit (s,h,m,y), such as '10d' for 10 days * STATES : comma separated list of task states to touch with the cleanup, by default only stopped tasks are covered, special value all can be used to clean the tasks, disregarding their states * NOOP : set to "true" if the task should not actually perform the deletion * VERBOSE : set to "true" for more verbose output * BATCH_SIZE : the size of batches the tasks get processed in (1000 by default) * TASK_BACKUP : set to "true" or "false" to enable/disable task backup If none of TASK_SEARCH, BEFORE, STATES is specified, the tasks will be cleaned based configuration in settings Expected results: There should no reference shown regarding 'BEFORE' statement, as it seems this is deprecated [1]. In addition, there should be an information, that the time-value of 'started_at' will be referenced. Also it's not really clear, how the AFTER keyword is working. What are the time units (s,h,m,y), when directly afterwards we talk about 'd'? If this is just an example list, it should be declared as such (like (e.g. s = seconds, h = hours, d = days, ...) Additional info: [1]: https://projects.theforeman.org/issues/8144