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:
If a Satellite is doing a lot of work, production.log may show a message with the string "some executors are not responding, check /foreman_tasks/dynflow/status".
This prints a message, and also prints a long stack trace. However, there is no action for the Satellite administrator to perform besides waiting for all of the work to complete.
It would be better if this message was only printed if user intervention is required. If foreman-tasks is busy, restarting it can create further problems.
Version-Release number of selected component (if applicable): 6.3.1
I am not sure how to make this happen reliably, but if you kick off a large number of registrations you can make it happen since foreman-tasks does fact processing and pkg profile upload.
NOTE: I put this bug in tasks plugin because I couldn't find a better category, but the check itself happens in katello.