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.
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 1260963https://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.
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
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