Chapter 11. Host Management Without Goferd and Katello Agent
goferd service that is used by the Katello agent to manage packages on content hosts consumes large amount of resources. To reduce memory and CPU load on content hosts, you can manage packages through remote execution.
Note that the Katello agent is deprecated and will be removed in a future Satellite version; therefore, using remote execution will be the only way to manage packages on hosts.
- You have enabled the Satellite Tools 6.7 repository on Satellite Server. For more information, see Enabling the Satellite Tools 6.7 Repository in Installing Satellite Server from a Connected Network.
- You have synchronized the Satellite Tools 6.7 repository on Satellite Server. For more information, see Synchronizing the Satellite Tools 6.7 Repository in Installing Satellite Server from a Connected Network.
- You have enabled the Satellite Tools 6.7 repository on content hosts.
katello-host-toolspackage on content hosts:
# yum install katello-host-tools
Stop the goferd service on content hosts:
# systemctl stop goferd.service
Disable the goferd service on content hosts:
# systemctl disable goferd.service
Remove the Katello agent on content hosts:Warning
If your host is installed on Red Hat Virtualization version 4.4 or lower, do not remove the
katello-agentpackage because the removed dependencies corrupt the host.
# yum remove katello-agent
- Distribute the SSH keys to the content hosts. For more information, see Section 10.3, “Distributing SSH Keys for Remote Execution”.
- In the Satellite web UI, navigate to Administer > Settings.
- Select the Content tab.
- Set the Use remote execution by default parameter to Yes.
The Satellite server now uses host management by remote execution instead of goferd.
The following applies if you are using the
hammer command to push errata. The
hammer command is dependent on goferd to manage errata on content hosts. As a workaround, use the Satellite remote execution feature to apply errata.
For example, enter the following command to perform a
yum -y update on host123.example.org:
# hammer job-invocation create \ --job-template "Run Command - SSH Default" \ --inputs command="yum -y update" \ --search-query "name ~ host123" Job invocation 24 created [.........................................] [100%] 1 task(s), 1 success, 0 fail