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-25 06:33:20 UTC
1. Proposed title of this feature request
[RFE] print applied filter on task export
3. What is the nature and description of the request?
There are different filters, some are default, some are configured using ENV variables when running task export. But it's not always clear, what type of filter is applied.
for example:
1) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=all TASK_DAYS=3 -> 16 tasks
2) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' TASK_DAYS=3 -> 2822 tasks
3) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=ALL TASK_DAYS=3 -> 16 tasks
4) foreman-rake foreman_tasks:export_tasks TASK_DAYS=3 -> 2835 tasks
5) foreman-rake foreman_tasks:export_tasks -> 7396 tasks
6) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' -> 32153 tasks
4. Why does the customer need this? (List the business requirements here)
To avoid confusion and mistakes
5. How would the customer like to achieve this? (List the functional requirements here)
Print the applied filter when running the command. Similar to cleanup-task
foreman-rake foreman_tasks:cleanup NOOP=true VERBOSE=true AFTER=60d TASK_SEARCH=''
...
[noop] deleting all tasks matching filter started_at < "2019-04-25 09:12:13" AND state = stopped
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
When the command is executed, it should print the applied filter on stdout.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap
9. Is the sales team involved in this request and do they have any additional input?
no
10. List any affected packages or components.
tfm-rubygem-foreman-tasks
11. Would the customer be able to assist in testing this functionality if implemented?
sure
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-2020:1454
1. Proposed title of this feature request [RFE] print applied filter on task export 3. What is the nature and description of the request? There are different filters, some are default, some are configured using ENV variables when running task export. But it's not always clear, what type of filter is applied. for example: 1) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=all TASK_DAYS=3 -> 16 tasks 2) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' TASK_DAYS=3 -> 2822 tasks 3) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=ALL TASK_DAYS=3 -> 16 tasks 4) foreman-rake foreman_tasks:export_tasks TASK_DAYS=3 -> 2835 tasks 5) foreman-rake foreman_tasks:export_tasks -> 7396 tasks 6) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' -> 32153 tasks 4. Why does the customer need this? (List the business requirements here) To avoid confusion and mistakes 5. How would the customer like to achieve this? (List the functional requirements here) Print the applied filter when running the command. Similar to cleanup-task foreman-rake foreman_tasks:cleanup NOOP=true VERBOSE=true AFTER=60d TASK_SEARCH='' ... [noop] deleting all tasks matching filter started_at < "2019-04-25 09:12:13" AND state = stopped 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. When the command is executed, it should print the applied filter on stdout. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? no 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? asap 9. Is the sales team involved in this request and do they have any additional input? no 10. List any affected packages or components. tfm-rubygem-foreman-tasks 11. Would the customer be able to assist in testing this functionality if implemented? sure