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.
DescriptionJustin Sherrill
2017-08-16 17:49:51 UTC
Description of problem:
It appears that puppet reports cause all statuses to be updated:
https://github.com/theforeman/foreman/blob/develop/app/services/report_importer.rb#L42
On a heavily loaded system this could mean this is being called 100s of times per second. This is a fairly slow operation to be doing when not necessary.
puppet reports should only refresh statuses that are relevant to them
Version-Release number of selected component (if applicable):
6.2.11
How reproducible:
always
Comment 6Satellite Program
2017-08-17 10:17:59 UTC
Upstream bug assigned to lzap
Comment 7Satellite Program
2017-08-17 10:18:02 UTC
Upstream bug assigned to lzap
Comment 9Satellite Program
2017-08-24 10:18:26 UTC
=== HOTFIX INSTRUCTIONS FOR SATELLITE 6.2.11 ONLY ===
1. Download attachment file bz1482204-hotfix-rpms-el7sat.tar.xz or bz1482204-hotfix-rpms-el6sat.tar.xz depending on your Satellite host OS version
2. Stop Satellite services
katello-service stop
3. Extract the tarball and install the packages in Satellite
4. Restart Satellite services
katello-service start
Verified on Satellite 6.2.14, only HostStatus::ConfigurationStatus is marked for refresh after completed puppet report. Also logging is now more informative, e.g.:
2018-01-12 03:29:18 11f58ac7 [app] [I] Imported report for ...redhat.com in 0.06 seconds, status refreshed in 0.02 seconds
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-2018:0273