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.
DescriptionPradeep Kumar Surisetty
2017-01-24 16:01:27 UTC
Description of problem:
Forman-debug
Version-Release number of selected component (if applicable):
With scale >6000 hosts takes > 60 mins to complete foreman-debug
Need light weight foreman-debug
How reproducible:
Steps to Reproduce:
1. foreman-debug takes longer time n
2.
3.
Actual results:
Expected results:
Additional info:
Comment 4Pradeep Kumar Surisetty
2017-01-25 16:24:39 UTC
Have 150k foreman-tasks which might be taking long time to export.
As a workaround, I suggest you to review old tasks cleanup configuration, it was broken in 6.2
foreman-rake foreman_tasks:cleanup
See description in
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.9.*/lib/foreman_tasks/tasks/cleanup.rake
By default it does not delete ANY tasks which are in error/failed/stuck state, therefore the queue can easily grow fast. In that case provide more aggressive deletion options.
Alternative workaround, delete this block
https://github.com/Katello/katello-packaging/pull/329/files#diff-27141c04050ed31299a2296657e4769cL85
from the
/usr/share/foreman/script/foreman-debug.d/katello-debug.sh
file and foreman-debug will be fast again.
This will be fixed in Satellite 6.3 where we only dump SQL data tables which is fast.
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-2018:0336