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:
When customer patches around 60 servers simultaneously from Satellite, many of them get to the "Uploading Tracer Profile" step around the same time, and some clients have delays of over 15 minutes. It is also possible to reproduce this by running a remote execution "katello-tracer-upload" command on multiple hosts.
Version-Release number of selected component (if applicable): Satellite 6.3.5
How reproducible: Consistently
Steps to Reproduce:
1. Have around 160 Satellite clients with katello-host-tools-tracer installed.
2. Create a Remote Execution job to run on the 160 clients and run the command "time katello-tracer-upload", with a 15 minute time out.
Actual results: In customers environment, 3 of the servers timed out after 15 minutes, and 2 servers ran for over 5 minutes.
Expected results: Servers not taking over 15 minutes to run katello-host-tools-tracer
Additional info:
Customer ran the same Remote execution job, but set the concurrency level to 1, so that it only ran on one server at a time, and did not have any failures or delays.
See also: https://community.theforeman.org/t/katello-tracer-troubleshoot/8676
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 (Important: Satellite 6.8 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-2020:4366