Bug 1368677 - restarting goferd on client forces applicability regeneration
Summary: restarting goferd on client forces applicability regeneration
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.1.9
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: Unspecified
Assignee: Chris Duryee
QA Contact: jcallaha
Depends On:
Blocks: 1368746 1379341
TreeView+ depends on / blocked
Reported: 2016-08-20 15:30 UTC by Chris Duryee
Modified: 2019-06-13 21:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1368746 (view as bug list)
Last Closed: 2016-09-27 09:03:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Ruby Patch File (1.19 KB, application/mbox)
2016-08-21 22:23 UTC, Mike McCune
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1938 normal SHIPPED_LIVE Satellite 6.1.10 bug fix update 2016-09-27 12:56:10 UTC

Description Chris Duryee 2016-08-20 15:30:41 UTC
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.

Comment 3 Mike McCune 2016-08-21 22:04:55 UTC
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.

Comment 4 Mike McCune 2016-08-21 22:23:57 UTC
Created attachment 1192719 [details]
Ruby Patch File

Comment 5 Mike McCune 2016-08-21 22:37:39 UTC

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

Comment 6 Mike McCune 2016-08-21 22:38:10 UTC
once applied, Applicability Calculation will only occur if the set of repos changed on the client system.

Comment 10 jcallaha 2016-09-20 16:00:39 UTC
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.

Comment 12 errata-xmlrpc 2016-09-27 09:03:53 UTC
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.


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