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.
Description of problem:
Due to the previous misunderstanding, users were deleting the foreman tasks directly from the foreman-rake console using ".destroy" function. This has cause huge performance impact to the Satellite when the orphan dynflow tasks are accumulated to thousands.
I had seen 5 or 6 cases that Satellite suffering from dynflow performance issue due to this issue and I believe there will be more. This is the reason that I decide to file this bug.
High unfinished orphan dynflow tasks usually cause the following issues.
- Host registration timeout.
- Very slow content view publish. Running for a day or more.
In the private note of KCS "https://access.redhat.com/solutions/2755731" has suggested a way to clean up the orphan dynflow tasks. I would like to suggest to add this code into the foreman task clean up script so that the orphan tasks clean up can be run in the cron job. This will prevent a lot of cases to be opened and will automatically fix performance issue for a lot of users.
-----------------
batch_size = 1000
persistence = ForemanTasks.dynflow.world.persistence
adapter = persistence.adapter
plans_without_tasks = adapter.db.fetch("select dynflow_execution_plans.uuid from dynflow_execution_plans left join foreman_tasks_tasks on (dynflow_execution_plans.uuid = foreman_tasks_tasks.external_id) where foreman_tasks_tasks.id IS NULL")
deleted = 0
total = plans_without_tasks.count
plans_without_tasks.all.map{|x| x[:uuid]}.in_groups_of(batch_size, false).each do |uuids|
delete_count = persistence.delete_execution_plans({ 'uuid' => uuids }, batch_size)
deleted += delete_count
puts "deleted #{deleted} out of #{total}"
end
----------------
The performance issue is fixed after deleting the orphan dynflow tasks, such as host registration was previously timeout will finish in seconds.