Chapter 5. Updating Satellite Server, Capsule Server, and Content Hosts
Use this chapter to update your existing Satellite Server, Capsule Server, and Content Hosts to a new minor version, for example, from 6.8.0 to 6.8.1.
Updates patch security vulnerabilities and minor issues discovered after code is released, and are often fast and non-disruptive to your operating environment.
Before updating, back up your Satellite Server and all Capsule Servers. For more information, see Backing Up Satellite Server and Capsule Server in the Administering Red Hat Satellite guide.
5.1. Updating Satellite Server
Prerequisites
- Ensure that you have synchronized Satellite Server repositories for Satellite, Capsule, and Satellite Tools 6.8.
- Ensure each external Capsule and Content Host can be updated by promoting the updated repositories to all relevant Content Views.
If you customize configuration files, manually or use a tool such as Hiera, these customizations are overwritten when the installation script runs during upgrading or updating. You can use the --noop
option with the satellite-installer script to test for changes. For more information, see the Red Hat Knowledgebase solution How to use the noop option to check for changes in Satellite config files during an upgrade.
Updating Satellite Server to the Next Minor Version
To Update Satellite Server:
Ensure the Satellite Maintenance repository is enabled:
# subscription-manager repos --enable \ rhel-7-server-satellite-maintenance-6-rpms
Ensure that the
rubygem-foreman_maintain
package that providessatellite-maintain
is installed and up to date:# yum install rubygem-foreman_maintain
Check the available versions to confirm the next minor version is listed:
# satellite-maintain upgrade list-versions
Use the health check option to determine if the system is ready for upgrade. On first use of this command,
satellite-maintain
prompts you to enter the hammer admin user credentials and saves them in the/etc/foreman-maintain/foreman-maintain-hammer.yml
file.# satellite-maintain upgrade check --target-version 6.8.z
Review the results and address any highlighted error conditions before performing the upgrade.
Because of the lengthy update time, use a utility such as
screen
to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. For more information about using the screen command, see How do I use the screen command? article in the Red Hat Knowledge Base.If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the
/var/log/foreman-installer/satellite.log
file to check if the process completed successfully.Perform the upgrade:
# satellite-maintain upgrade run --target-version 6.8.z
Check when the kernel packages were last updated:
# rpm -qa --last | grep kernel
Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:# satellite-maintain service stop # reboot
5.2. Updating Disconnected Satellite Server
Prerequisites
- Before syncing the following repositories, set the download policy to Immediate. This is required because Satellite downloads all packages only during synchronization of repositories with the immediate download policy.
Ensure that you have synchronized the following Satellite Server repositories for Satellite, Capsule, and Satellite Tools 6.8:
- rhel-7-server-rpms
- rhel-7-server-satellite-6.8-rpms
- rhel-7-server-satellite-maintenance-6-rpms
- rhel-server-rhscl-7-rpms
rhel-7-server-ansible-2.9-rpms
For more information about configuring download policies, see https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8/html/content_management_guide/importing_red_hat_content#changing_the_download_policy_for_a_repository in the Content Management guide.
Ensure no Red Hat repositories are enabled by entering the command:
# yum repolist
Updating Disconnected Satellite Server to the Next Minor Version
Create a new configuration file as follows:
# vi /etc/yum.repos.d/redhat-local.repo [rhel-7-server-ansible-2.9-rpms] name=Ansible 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64 baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/ansible/2.9/os/ enabled=1 [rhel-7-server-rpms] name=Red Hat Enterprise Linux 7 Server RPMs x86_64 baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/os/ enabled=1 [rhel-7-server-satellite-6.8-rpms] name=Red Hat Satellite 6 for RHEL 7 Server RPMs x86_64 baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/satellite/6.8/os/ enabled=1 [rhel-7-server-satellite-maintenance-6-rpms] name=Red Hat Satellite Maintenance 6 for RHEL 7 Server RPMs x86_64 baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/sat-maintenance/6/os/ enabled=1 [rhel-server-rhscl-7-rpms] name=Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/ enabled=1
In the configuration file, replace
Default_Organization
in thebaseurl
with the correct organization label. To obtain the organization label, enter the commmand:# ls /var/lib/pulp/published/yum/https/repos/
Ensure that the
rubygem-foreman_maintain
package that providessatellite-maintain
is installed and up to date:# yum install rubygem-foreman_maintain
Check the available versions to confirm the next minor version is listed:
# satellite-maintain upgrade list-versions
Use the health check option to determine if the system is ready for the upgrade. On the first use of this command,
satellite-maintain
prompts you to enter the hammer admin user credentials and saves them in the/etc/foreman-maintain/foreman-maintain-hammer.yml
file.# satellite-maintain upgrade check --target-version 6.8.z
Review the results and address any highlighted error conditions before performing the upgrade.
Because of the lengthy update time, use a utility such as
screen
to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. For more information about using the screen command, see How do I use the screen command? article in the Red Hat Knowledge Base.If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the
/var/log/foreman-installer/satellite.log
file to check if the process completed successfully.Perform the upgrade:
# satellite-maintain upgrade run --target-version 6.8.z
Check when the kernel packages were last updated:
# rpm -qa --last | grep kernel
Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:# satellite-maintain service stop # reboot
5.3. Updating Capsule Server
Use this procedure to update Capsule Servers to the next minor version.
Procedure
Update the
gofer
package:# satellite-maintain packages install gofer
Restart the
goferd
service:# systemctl restart goferd
Ensure that the Satellite Maintenance repository is enabled:
# subscription-manager repos --enable \ rhel-7-server-satellite-maintenance-6-rpms
Check the available versions to confirm the next minor version is listed:
# satellite-maintain upgrade list-versions
Use the health check option to determine if the system is ready for upgrade:
# satellite-maintain upgrade check --target-version 6.8.z
Review the results and address any highlighted error conditions before performing the upgrade.
Because of the lengthy update time, use a utility such as
screen
to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. For more information about using the screen command, see How do I use the screen command? article in the Red Hat Knowledge Base.If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the
/var/log/foreman-installer/satellite.log
file to check if the process completed successfully.Perform the upgrade:
# satellite-maintain upgrade run --target-version 6.8.z
Check when the kernel packages were last updated:
# rpm -qa --last | grep kernel
Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:# satellite-maintain service stop # reboot
5.4. Updating Content Hosts
Updating Content Hosts to the Next Minor Version
To Update a Content Host, enter the following commands:
Update the
gofer
package:# yum update gofer
Restart goferd:
# systemctl restart goferd
Update all packages:
# yum update
Optional: If a kernel update occurred since the last reboot, reboot the system:
# reboot