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:
If you restart goferd on a system, errata applicability will be regenerated. This can cause performance issues, especially if you have a large number of hosts.
Version-Release number of selected component (if applicable): 6.1.9
How reproducible: every time
Steps to Reproduce:
1. register host to Satellite, ensure goferd is running
2. restart goferd
3. check tasks list
Actual results: applicability regeneration task is created
Expected results: applicability regeneration should only happen when list of enabled repos changes
Additional info: the task list is the "true" way to check this, but a quick way is to tail /var/log/httpd/foreman-ssl_access_ssl.log on the server and restart goferd on the client. If you see a line like "POST /pulp/api/v2/consumers/actions/content/regenerate_applicability//", it means a regenerate was fired.
To expand on this bug:
anything that modifies the redhat.repo file on the client will cause this applicability generation to occur, even if the set of enabled/disable repos does not change.
** 6.1 HOTFIX PATCH INSTRUCTIONS **
The above attached patch file will only work with Satellite 6.1.X
1) download the patch from Comment #4 to your Satellite server
2) Copy to /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.2.0.<version number>
3) cd /opt/rh/ruby193/root/usr/share/gems/gems/katello-2.2.0.<version number>
4) execute patch:
# patch -p1 < 1368677-1.patch
patching file app/models/katello/system.rb
5) Restart services
Verified in Satellite 6.1.10.
Performed the steps required using docker-based content hosts and did not see any new applicability regeneration in the logs.
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/RHBA-2016:1938