Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Updating Red Hat Satellite

Red Hat Satellite 6.17

Update Satellite Server and Capsule to a new minor release

Red Hat Satellite Documentation Team

Abstract

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

Providing feedback on Red Hat documentation
Copy link

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.

Prerequisites

Procedure

  1. Click the following link: Create Issue. If Jira displays a login error, log in and proceed after you are redirected to the form.
  2. Complete the Summary and Description 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.
  3. Click Create.

You can update your Satellite Server and Capsule Server to a new patch release version, such as from 6.17.0 to 6.17.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
Copy link

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

If you customize configuration files, manually or using a tool such as Hiera, these changes are overwritten when the maintenance script runs during upgrading or updating. 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.17-for-rhel-9-x86_64-rpms
    Copy to Clipboard Toggle word wrap

  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
    Copy to Clipboard Toggle word wrap

    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
    Copy to Clipboard Toggle word wrap

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

    # reboot
    Copy to Clipboard Toggle word wrap

Additional resources

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.

Prerequisites

You can update your disconnected Satellite on Red Hat Enterprise Linux 9 by synchronizing the required repositories on the connected Satellite and syncing the content to the disconnected Satellite by using syncable exports.

Procedure on the connected Satellite Server

  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.17-for-rhel-9-x86_64-rpms
    • satellite-maintenance-6.17-for-rhel-9-x86_64-rpms

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

  2. List the repositories to identify their IDs: 

    $ hammer repository list \
--organization-label My_Organization_Label
    Copy to Clipboard Toggle word wrap

  3. Export the repositories in the syncable format: 

    $ hammer content-export complete repository \
--format syncable \
--id My_Repository_ID
    Copy to Clipboard Toggle word wrap
  4. Copy the exported directories to the disconnected Satellite Server.

Procedure on the disconnected Satellite Server

  1. Locate the copied 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.17-for-rhel-9-x86_64-rpms]
name=Red Hat Satellite 6.17 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.17/os/

[satellite-maintenance-6.17-for-rhel-9-x86_64-rpms]
name=Red Hat Satellite Maintenance 6.17 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.17/os/
    Copy to Clipboard Toggle word wrap

  3. Upgrade satellite-maintain to the next version: 

    # satellite-maintain self-upgrade --maintenance-repo-label=satellite-maintenance-6.17-for-rhel-9-x86_64-rpms
    Copy to Clipboard Toggle word wrap

  4. Evaluate that the system is ready for update. 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. 

    # satellite-maintain update check --whitelist="repositories-validate,repositories-setup"
    Copy to Clipboard Toggle word wrap
  5. Review the results and resolve any errors before proceeding with the update.

  6. 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.

  7. Perform the update: 

    # satellite-maintain update run --whitelist="repositories-validate,repositories-setup"
    Copy to Clipboard Toggle word wrap

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

    # reboot
    Copy to Clipboard Toggle word wrap

Additional resources

Chapter 4. Updating Capsule Server
Copy link

Update Capsule Servers to the next patch version.

Procedure

  1. Synchronize the satellite-capsule-6.17-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.17-for-rhel-9-x86_64-rpms
    Copy to Clipboard Toggle word wrap

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

    # satellite-maintain update check
    Copy to Clipboard Toggle word wrap

    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
    Copy to Clipboard Toggle word wrap

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

    # reboot
    Copy to Clipboard Toggle word wrap

Legal Notice
Copy link

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, 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, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat