Description of problem:
It appears that puppet reports cause all statuses to be updated:
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):
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20622 has been resolved.
=== 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
3. Extract the tarball and install the packages in Satellite
4. Restart Satellite services
This bug has been fixed in 1.15.4 upstream release, it is part of latest drop. Moving on.
nope, this is the 6.2 clone
Yeah, sorry. Done.
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
HOTFIX BUILDS FOR 6.2.13:
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.