This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1649047 - Default debug export interval to 1 month instead of 6 and maximum 1000 entries
Summary: Default debug export interval to 1 month instead of 6 and maximum 1000 entries
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Peter Ondrejka
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-12 19:00 UTC by Pavel Moravec
Modified: 2024-06-05 21:30 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-0.14.4.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:30:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25434 0 None None None 2018-11-13 12:00:24 UTC
Foreman Issue Tracker 26415 0 None None None 2019-03-20 10:26:06 UTC
Github sosreport sos pull 1623 0 None None None 2019-03-27 13:17:22 UTC
Red Hat Issue Tracker   SAT-25399 0 None Migrated None 2024-06-05 21:30:57 UTC

Description Pavel Moravec 2018-11-12 19:00:26 UTC 
Description of problem:
In case a Satellite generates many (foreman) tasks per day, foreman-debug will 1) take too long to execute, and 2) generate huge *.csv files. That makes troubleshooting of Satellite issues slower. We shall limit task search in 60-dynflow_debug (only? also? rather?) by number of tasks.

Also from the same rank, tasks cleanup should consider (or at least offer option to) deleting all-except-newest N tasks, instead of time-based filter.

Since I expect there is no one solution that fits all, f-d and cleanup should be ideally bit flexible (i.e. "collect X tasks or tasks from past Y days, whatever is smaller" for f-d and similarly for the cleanup).


Version-Release number of selected component (if applicable):
Sat 6.4


How reproducible:
100%


Steps to Reproduce:
1. Generate too many tasks (i.e. tens of thousands) per day.
2. take foreman-debug
3. run tasks cleanup rake script


Actual results:
2. foreman-debug takes hours to complete, tarball is hundreds of MBs of size, *.csv files (tens of) GBs.
3. still too much tasks kept in db


Expected results:
2. f-d to complete in reasonable time, consuming reasonable disk space
3. only considerable number of tasks remain after the cleanup


Additional info:
Comment 1 Pavel Moravec 2018-11-12 19:08:12 UTC 
relevant but imho insufficient: https://projects.theforeman.org/issues/25434
Comment 2 Lukas Zapletal 2018-11-13 09:20:58 UTC 
Pavel, please don't create BZ for such a thing, just join our conversation on github. This is indeed a great idea, I will add it to the patch immediately. Will show up in Satellite 6.6 then.
Comment 6 Satellite Program 2018-12-17 17:04:58 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25434 has been resolved.
Comment 11 Bryan Kearney 2019-03-19 14:03:21 UTC 
Upstream bug assigned to lzap
Comment 12 Lukas Zapletal 2019-03-20 10:26:07 UTC 
PR pending: https://projects.theforeman.org/issues/26415
Comment 13 Pavel Moravec 2019-03-27 13:17:23 UTC 
FYI this has been updated in sosreport since (future) RHEL7.7.
Comment 15 Eric Helms 2024-06-05 21:30:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.