Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1482204 - Puppet reports recalculate all statuses (including errata status)
Puppet reports recalculate all statuses (including errata status)
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hosts (Show other bugs)
6.2.10
Unspecified Unspecified
high Severity high (vote)
: 6.2.14
: Unused
Assigned To: Lukas Zapletal
Peter Ondrejka
http://projects.theforeman.org/issues...
: FieldEngineering, PrioBumpField, Triaged
Depends On:
Blocks: 1482208
  Show dependency treegraph
 
Reported: 2017-08-16 13:49 EDT by Justin Sherrill
Modified: 2018-02-07 13:48 EST (History)
14 users (show)

See Also:
Fixed In Version: foreman-1.11.0.86-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1530696 (view as bug list)
Environment:
Last Closed: 2018-02-05 08:54:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
foreman hotfix rpms for el7sat (7.83 MB, application/x-xz)
2017-08-28 11:25 EDT, Adam Price
no flags Details
foreman hotfix rpms for el6sat (8.83 MB, application/x-xz)
2017-08-28 11:25 EDT, Adam Price
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 20622 None None None 2017-08-17 05:03 EDT
Red Hat Product Errata RHSA-2018:0273 normal SHIPPED_LIVE Important: Red Hat Satellite 6 security, bug fix, and enhancement update 2018-02-07 19:35:29 EST

  None (edit)
Description Justin Sherrill 2017-08-16 13:49:51 EDT
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 6 pm-sat@redhat.com 2017-08-17 06:17:59 EDT
Upstream bug assigned to lzap@redhat.com
Comment 7 pm-sat@redhat.com 2017-08-17 06:18:02 EDT
Upstream bug assigned to lzap@redhat.com
Comment 9 pm-sat@redhat.com 2017-08-24 06:18:26 EDT
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20622 has been resolved.
Comment 12 Adam Price 2017-08-28 11:30:38 EDT
=== 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
Comment 16 Lukas Zapletal 2018-01-08 08:56:23 EST
This bug has been fixed in 1.15.4 upstream release, it is part of latest drop. Moving on.
Comment 17 Evgeni Golov 2018-01-08 09:18:46 EST
nope, this is the 6.2 clone
Comment 18 Lukas Zapletal 2018-01-09 02:34:41 EST
Yeah, sorry. Done.
Comment 20 Peter Ondrejka 2018-01-12 07:36:33 EST
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
Comment 21 Lukas Zapletal 2018-01-17 09:12:31 EST
HOTFIX BUILDS FOR 6.2.13:

http://people.redhat.com/~lzapleta/hotfix/status-all-1482204/
Comment 24 errata-xmlrpc 2018-02-05 08:54:34 EST
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

Note You need to log in before you can comment on or make changes to this bug.