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 you run 'hammer ping' on a busy system, foreman-tasks may show as being dead if it is busy processing lots of tasks. This can result in confusion.


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

How reproducible: intermittent

Steps to Reproduce:
1. create a lot of tasks, for example lots of package profile uploads
2. check hammer ping frequently

Actual results: hammer ping will occasionally time out after 2 seconds and show 'FAIL' for foreman-tasks


Expected results: hammer ping only fails for foreman-tasks if something requires user intervention.


Additional info: This might be similar to https://bugzilla.redhat.com/show_bug.cgi?id=1420651 but I am not sure if it's the same root cause.

*** Bug 1588779 has been marked as a duplicate of this bug. ***

Created redmine issue http://projects.theforeman.org/issues/23926 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23926 has been resolved.

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-2019:1222