Updating Red Hat Satellite

Red Hat Satellite 6.18

Update Satellite Server and Capsule to a new minor release

Abstract

Update Red Hat Satellite Server and Capsule Server regularly to ensure optimal performance and security.

Providing feedback on Red Hat documentation

We appreciate your feedback on our documentation. Let us know how we can improve it.

Use the Create Issue form in Red Hat Jira to provide your feedback. The Jira issue is created in the Red Hat Satellite Jira project, where you can track its progress.

Procedure

  1. Log in to Content from id.atlassian.com is not included.Atlassian Jira.
  2. Click the following link: Content from redhat.atlassian.net is not included.Create Issue.
  3. Complete the Summary, Description, and Reporter fields. In the Description field, include the documentation URL, chapter or section number, and a detailed description of the issue. Do not modify any other fields in the form.
  4. Click Create.

Chapter 1. Updating Satellite to the next patch version

You can update your Satellite Server and Capsule Server to a new patch release version, such as from 6.18.0 to 6.18.1, by using the Satellite maintain tool. The patch releases are non-disruptive to your operating environment and often fast.

Always update Satellite Server, Capsule Server, or the operating system by using satellite-maintain update. If there are pending Satellite Server updates, updating the operating system will update both.

Important

Perform updates regularly to resolve security vulnerabilities and other issues.

Chapter 2. Updating Satellite Server

Update your connected Satellite Server to the next patch version. You can follow this process to update the underlying operating system between minor release versions. For information to update a disconnected Satellite setup, see Chapter 3, Updating a disconnected Satellite Server.

Prerequisites

Warning

Note that the satellite-installer is executed during an upgrade or update. Any files managed by satellite-installer are overwritten. Check if you have any manual changes that would be overwritten by satellite-installer. You can use the --noop option with the satellite-installer 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.

Procedure

  1. Ensure the Satellite Maintenance repository is enabled: 

    # subscription-manager repos --enable \
satellite-maintenance-6.18-for-rhel-9-x86_64-rpms

  2. Use the health check option to determine if the system is ready for update. 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 update check

    Review the results and address any highlighted error conditions before performing the update.

  3. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the update progress without staying connected to the command shell continuously.

    If you lose connection to the command shell where the update 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.

  4. Perform the update: 

    # satellite-maintain update run

  5. If the satellite-maintain command told you to reboot, then reboot the system: 

    # reboot

Additional resources

Chapter 3. Updating a disconnected Satellite Server

Update your air-gapped Satellite setup where the connected Satellite Server, which synchronizes content from CDN, is air-gapped from a disconnected Satellite Server, to the next patch version. You can follow this process to update the underlying operating system between minor release versions.

Important

Back up your disconnected Satellite Server before updating it. For more information, see Backing Up Satellite Server and Capsule Server in Administering Red Hat Satellite.

3.1. Exporting repositories from the connected Satellite Server

Export the required repositories on the connected Satellite Server to transfer to the disconnected Satellite Server.

Procedure

  1. Synchronize the following repositories on your connected Satellite Server:

    • rhel-9-for-x86_64-baseos-rpms
    • rhel-9-for-x86_64-appstream-rpms
    • satellite-6.18-for-rhel-9-x86_64-rpms
    • satellite-maintenance-6.18-for-rhel-9-x86_64-rpms

    Ensure to set the download policy to Immediate for each repository.

  2. List the repositories to identify their IDs: 

    $ hammer repository list \
--organization-label My_Organization_Label

  3. Export each repository in the syncable format: 

    $ hammer content-export complete repository \
--format syncable \
--id My_Repository_ID
  4. Transfer the exported directories to your disconnected Satellite Server.

3.2. Preparing repositories on the disconnected Satellite Server

Create local repositories on your disconnected Satellite Server.

Prerequisites

  • You have transferred the exported directories to your disconnected Satellite Server.

Procedure

  1. Locate the transferred exported directories.

  2. Create the /etc/yum.repos.d/update.repo file and update the baseurl values to point to the local file system: 

    [rhel-9-for-x86_64-baseos-rpms]
name=Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)
enabled=1
metadata_expire=-1
gpgcheck=0
baseurl=file:///BaseOS_Export_Location/content/dist/rhel9/9/x86_64/baseos/os

[rhel-9-for-x86_64-appstream-rpms]
name=Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
enabled=1
metadata_expire=-1
gpgcheck=0
baseurl=file:///AppStream_Export_Location/content/dist/rhel9/9/x86_64/appstream/os

[satellite-6.18-for-rhel-9-x86_64-rpms]
name=Red Hat Satellite 6.18 for RHEL 9 Server RPMs x86_64
enabled=1
metadata_expire=-1
gpgcheck=0
baseurl=file:///Satellite_Export_Location/content/dist/layered/rhel9/x86_64/satellite/6.18/os/

[satellite-maintenance-6.18-for-rhel-9-x86_64-rpms]
name=Red Hat Satellite Maintenance 6.18 for RHEL 9 Server RPMs x86_64
enabled=1
metadata_expire=-1
gpgcheck=0
baseurl=file:///Satellite_Maintenance_Export_Location/content/dist/layered/rhel9/x86_64/sat-maintenance/6.18/os/

3.3. Performing the update of the disconnected Satellite Server

Evaluate that the system is ready for update and perform the update of the disconnected Satellite Server. Your Satellite Server does not require internet access to perform the update.

Prerequisites

  • You have prepared the required repositories on the disconnected Satellite Server.

Procedure

  1. Evaluate that the system is ready for update: 

    # satellite-maintain update check --whitelist="repositories-validate,repositories-setup"

    The first time you run this command, satellite-maintain prompts you to enter the Hammer admin user credentials and saves them to /etc/foreman-maintain/foreman-maintain-hammer.yml.

  2. Review the results and resolve any errors before proceeding with the update.

  3. Due to the lengthy update time, use a utility such as tmux to suspend and resume the session as needed. By using such utility, you can monitor progress without maintaining a continuous connection to the command shell.

    If you lose connection to the command shell where the update command is running, check the /var/log/foreman-installer/satellite.log file to confirm whether the process completed successfully.

  4. Perform the update: 

    # satellite-maintain update run --whitelist="repositories-validate,repositories-setup"

  5. If the satellite-maintain command told you to reboot, then reboot the system: 

    # reboot

Additional resources

Chapter 4. Updating Capsule Server

Update Capsule Servers to the next patch version.

Procedure

  1. Synchronize the satellite-capsule-6.18-for-rhel-9-x86_64-rpms repository in the Satellite Server.
  2. Publish and promote a new version of the content view with which the Capsule is registered.

  3. Ensure that the Satellite Maintenance repository is enabled: 

    # subscription-manager repos --enable \
satellite-maintenance-6.18-for-rhel-9-x86_64-rpms

  4. Use the health check option to determine if the system is ready for update: 

    # satellite-maintain update check

    Review the results and address any highlighted error conditions before performing the update.

  5. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the update progress without staying connected to the command shell continuously.

    If you lose connection to the command shell where the update command is running, you can see the logged messages in the /var/log/foreman-installer/capsule.log file to check if the process completed successfully.

  6. Perform the update: 

    # satellite-maintain update run

  7. If the satellite-maintain command told you to reboot, then reboot the system: 

    # reboot

Legal Notice

Copyright © Red Hat.
Except as otherwise noted below, the text of and illustrations in this documentation are licensed by Red Hat under the Creative Commons Attribution–Share Alike 3.0 Unported license . If you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, the Red Hat logo, JBoss, Hibernate, and RHCE are trademarks or registered trademarks of Red Hat, LLC. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
XFS is a trademark or registered trademark of Hewlett Packard Enterprise Development LP or its subsidiaries in the United States and other countries.
The OpenStack® Word Mark and OpenStack logo are trademarks or registered trademarks of the Linux Foundation, used under license.
All other trademarks are the property of their respective owners.