Bug #19393: Need ability to completely disable goferd on managed clients - Katello - Foreman

Actions

Copy link

Bug #19393

closed

Need ability to completely disable goferd on managed clients

Added by Brad Buckingham about 8 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Justin Sherrill

Category:

Client/Agent

Target version:

Katello 3.4.1

Difficulty:

Triaged:

Bugzilla link:

1445403

Pull request:

https://github.com/Katello/katello-agent/pull/44, https://github.com/Katello/katello-packaging/pull/437

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1445403

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.

Related issues 1 (0 open — 1 closed)