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.10.0 to 6.10.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 Copy linkLink copied to clipboard!
Prerequisites
- Ensure that you have synchronized Satellite Server repositories for Satellite, Capsule, and Satellite Tools 6.10.
- 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
# subscription-manager repos --enable \ rhel-7-server-satellite-maintenance-6-rpms
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the available versions to confirm the next minor version is listed:
satellite-maintain upgrade list-versions
# satellite-maintain upgrade list-versions
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 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.10.z
# satellite-maintain upgrade check --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 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.10.z
# satellite-maintain upgrade run --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check when the kernel packages were last updated:
rpm -qa --last | grep kernel
# rpm -qa --last | grep kernel
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:satellite-maintain service stop reboot
# satellite-maintain service stop # reboot
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
5.2. Updating Disconnected Satellite Server Copy linkLink copied to clipboard!
This section describes the steps needed to update in an Air-gapped Disconnected setup where the connected Satellite Server (which synchronizes content from CDN) is air gapped from a disconnected Satellite Server.
Complete the following steps on the connected Satellite Server.
Ensure that you have synchronized the following repositories in your connected Satellite Server.
rhel-7-server-ansible-2.9-rpms rhel-7-server-rpms rhel-7-server-satellite-6.10-rpms rhel-7-server-satellite-maintenance-6-rpms rhel-server-rhscl-7-rpms
rhel-7-server-ansible-2.9-rpms rhel-7-server-rpms rhel-7-server-satellite-6.10-rpms rhel-7-server-satellite-maintenance-6-rpms rhel-server-rhscl-7-rpms
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Download the debug certificate of the organization and store it locally at, for example,
/etc/pki/katello/certs/org-debug-cert.pem
or a location of your choosing. Create a Yum configuration file under
/etc/yum.repos.d
with the following repository information:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
In the configuration file, replace
/etc/pki/katello/certs/org-debug-cert.pem
insslclientcert
andsslclientkey
with the location of the downloaded organization debug certificate. -
Update
satellite.example.com
with correct FQDN for your deployment. Replace
My_Organization
with the correct organization label in thebaseurl
. To obtain the organization label, enter the command:hammer organization list
# hammer organization list
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the
reposync
command:Copy to Clipboard Copied! Toggle word wrap Toggle overflow This downloads the contents of the repositories from the connected Satellite Server and stores them in the directory
~/Satellite-repos
. Thereposync
command in Red Hat Enterprise Linux 7 downloads the RPMs but not the Yum metadata.Because of this, you must manually run
createrepo
in each sub-directory ofSatellite-repos
. Make sure you have thecreaterepo
rpm installed. If not use the following command to install it.satellite-maintain packages install createrepo
# satellite-maintain packages install createrepo
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run the following command to create repodata in each sub-directory of
~/Satellite-repos
. :Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Verify that the RPMs have been downloaded and the repository data directory is generated in each of the sub-directories of
~/Satellite-repos
. Archive the contents of the directory
cd ~ tar czf Satellite-repos.tgz Satellite-repos
# cd ~ # tar czf Satellite-repos.tgz Satellite-repos
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Use the generated
Satellite-repos.tgz
file to upgrade in the disconnected Satellite Server.
Perform the following steps on the disconnected Satellite Server
-
Copy the generated
Satellite-repos.tgz
file to your disconnected Satellite Server Extract the archive to anywhere accessible by the
root
user. In the following example/root
is the extraction location.cd /root tar zxf Satellite-repos.tgz
# cd /root # tar zxf Satellite-repos.tgz
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create a Yum configuration file under
/etc/yum.repos.d
with the following repository information:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
In the configuration file, replace the
/root/Satellite-repos
with the extracted location. Check the available versions to confirm the next minor version is listed:
satellite-maintain upgrade list-versions
# satellite-maintain upgrade list-versions
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 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 --whitelist="check-upstream-repository,repositories-validate" --target-version 6.10.z
# satellite-maintain upgrade check --whitelist="check-upstream-repository,repositories-validate" --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - 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 --whitelist="check-upstream-repository,repositories-validate" --target-version 6.10.z
# satellite-maintain upgrade run --whitelist="check-upstream-repository,repositories-validate" --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check when the kernel packages were last updated:
rpm -qa --last | grep kernel
# rpm -qa --last | grep kernel
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:satellite-maintain service stop reboot
# satellite-maintain service stop # reboot
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
5.3. Updating Capsule Server Copy linkLink copied to clipboard!
Use this procedure to update Capsule Servers to the next minor version.
Procedure
Ensure that the Satellite Maintenance repository is enabled:
subscription-manager repos --enable \ rhel-7-server-satellite-maintenance-6-rpms
# subscription-manager repos --enable \ rhel-7-server-satellite-maintenance-6-rpms
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check the available versions to confirm the next minor version is listed:
satellite-maintain upgrade list-versions
# satellite-maintain upgrade list-versions
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Use the health check option to determine if the system is ready for upgrade:
satellite-maintain upgrade check --target-version 6.10.z
# satellite-maintain upgrade check --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 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.10.z
# satellite-maintain upgrade run --target-version 6.10.z
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Check when the kernel packages were last updated:
rpm -qa --last | grep kernel
# rpm -qa --last | grep kernel
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Optional: If a kernel update occurred since the last reboot, stop the
satellite-maintain
services and reboot the system:satellite-maintain service stop reboot
# satellite-maintain service stop # reboot
Copy to Clipboard Copied! Toggle word wrap Toggle overflow