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:
The puppet module puppet-access_insights_client generates excessive load in large Satellite deployments, by using `ensure => latest` rather than using `ensure => present` and relying on normal patching operations to update the package. In one customer case this was causing constant 100% CPU Utilization on Satellite.
The relevant RPM package is redhat-access-insights-puppet, which is shipped in Satellite repositories but (I believe) owned by Insights engineering.
The issue affects all currently shipped versions of the redhat-access-insights-puppet RPM although the logic is modified on the latest version of the module, such that only certain RHEL versions use the `ensure => latest` logic.
This issue would be resolved upstream via the open PR:
https://github.com/redhataccess/puppet-access_insights_client/pull/6
Version-Release number of selected component (if applicable):
redhat-access-insights-puppet RPM (all currently shipped versions)
How reproducible:
100%
For the latest shipped version of the RPM, the issue occurs on clients satisfying the below condition which results in using the manifest old.pp:
if (versioncmp($::operatingsystemrelease, '6.10') < 0 or
(versioncmp($::operatingsystemrelease, '7.0') >= 0 and versioncmp($::operatingsystemrelease, '7.5') < 0)) {
$class_name = 'old'
old.pp declares the package with `ensure => latest`, causing extraneous calls to Satellite checking for package updates. At large scale, the issue results in excessive utilization of Satellite resources.
Steps to Reproduce:
Using the 256GB RAM tuning profile for Satellite, running on hardware comparable to a 'very large' Satellite deployment, Install this puppet module on roughly 15,000+ Content Hosts with a mix of RHEL versions.
Actual results:
Puppet module is checking for updates to the insights-client RPM each time it runs, causing constant, excessive traffic on Satellite that results in 100% CPU utilization at scale
Expected results:
Puppet module ensures that the package is present, and relies on normally scheduled patching operations to update the insights-client RPM.
Verified in Satellite 6.7 Snap 16
The solution was to update the old manifest to check that packages were installed instead of latest.
cat /usr/share/puppet/modules/access_insights_client/manifests/old.pp
...
) {
package { $package_name:
ensure => installed,
}
...
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-2020:1454