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:
When running jobs on large number of hosts, slow checking of outputs can have severe impact on execution time of the entire job.


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


How reproducible:


Steps to Reproduce:
1. Run a job on 1k hosts outputting a single character each second for five minutes.
2. Run a job on 1k hosts outputting a single character into a temporary file each second for five minutes and reading it whole at the end.

Actual results:
The first job is by orders of magnitude slower than the second one.


Expected results:
The two jobs should take roughly the same amount of time to finish.


Additional info:
Job #1: 15:22:43 - 16:43:24 (almost hour and a half)
Job #2: 18:09:38 - 18:23:40 (roughly 15 minutes)

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

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

We actually have fixes ready now, reopening.

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

Checked on Satellite 7.0 snap 5, verified that the code pieces landed as expected

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 (Moderate: Satellite 6.11 Release), 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-2022:5498