Bug 1445403

Summary:	Need ability to completely disable goferd on managed clients
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	katello-agent	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.2.9	CC:	aperotti, bbuckingham, bkearney, brubisch, cdonnell, cwelton, egolov, ehelms, fgarciad, jcallaha, jsherril, kabbott, kdixon, pdwyer, peter.vreman, rplevka, swadeley, will_darton, zhunting
Target Milestone:	Unspecified	Keywords:	PrioBumpField, PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	katello-host-tools-3.0.0-5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1463809 (view as bug list)		Environment:
Last Closed:	2017-08-10 20:13:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1454352, 1463818
Bug Blocks:	1122832

Description Mike McCune 2017-04-25 15:23:05 UTC

Due to instability in gofer + qpid and our lack of ability to reliably resolve the following high visibility and severity bugs:

1) goferd continues to leak memory when qdrouterd is not accessible. Was supposedly fixed as per bz 1260963

https://bugzilla.redhat.com/show_bug.cgi?id=1318015

2) qpidd consuming huge memory during scale 

https://bugzilla.redhat.com/show_bug.cgi?id=1367735

we need to support the ability to have managed clients run without requiring goferd to be enabled. This will also help in environments that don't need goferd to perform updates and who are entirely relying on REX as a way to perform updates.

In the short term for 6.2 we may still require the installation of katello-agent but then allow the service level disabling of goferd and rely on a yum plugin, cron or some other mechanism to replace the existing applicability and enabled/disabled repository reports sent back to the server.

Comment 2 Mike McCune 2017-04-25 16:12:14 UTC

Main Use Case:

1) User registers via subscription-manager normally

2) A user installs katello-agent via yum and by default, goferd is started and enabled as a service daemon

3) User wishes to ensure goferd is not running on the client and runs: 
 systemctl stop goferd.service 
 systemctl disable goferd.service

4) User enables and disables repositories via 'subscription-manager repos' command

5) Applicability and errata updates are correctly displayed in the Satellite UI

6) User utilizes REX as a means to apply errata updates

7) Applicability and errata updates are correctly displayed in the Satellite UI after application of errata

Comment 3 Brad Buckingham 2017-04-26 14:21:19 UTC

Created redmine issue http://projects.theforeman.org/issues/19393 from this bug

Comment 5 Satellite Program 2017-06-06 20:09:53 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19393 has been resolved.

Comment 10 errata-xmlrpc 2017-08-10 20:13:02 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.

https://access.redhat.com/errata/RHBA-2017:2467