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:
The foreman_tasks:cleanup rake task runs as an executor. This means that during the task cleanup the rake task can actually start processing satellite's tasks. When the rake task exits it may (or may not) leave the tasks it was processing in some kind of bad state (abnormal termination?).


Version-Release number of selected component (if applicable):
I'm not aware of any recent change which could introduce this behavior, this probably affects all satellite versions.

How reproducible:
Always


Steps to Reproduce:
1. Go into dynflow console
2. Run foreman_tasks:cleanup rake task
3. Keep refreshing the page until a new world record appears

Actual results:
The world used by the rake task appears under executor worlds

Expected results:
The world used by the rake task appears under client worlds

Additional info:

Created redmine issue https://projects.theforeman.org/issues/25935 from this bug

@Adam: with what version were you able to reproduce this? I'm not lucky with neither sat 6.3, 6.4 nor 6.5 in production. This code should make sure only db:migrate and db:seed are using their own executor

https://github.com/dynflow/dynflow/blob/fef5ca352fc90027440b159b9719a91ef1eb468a/lib/dynflow/rails/configuration.rb#L85

I originally tested this from a git checkout in development environment and jumped to conclusions without verifying the behaviour in production. Now trying that in production I'm failing to reproduce the bug. So this is probably unrelated to the issues some of our customers are seeing. We can probably close the BZ, but I'd still keep the upstream issue around, even if just to bring the development environment's behaviour closer to production.

Closing as it's actually not reproducible in production. After analyzing the data from the case, it most probably looks like hitting this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1602110