Este contenido no está disponible en el idioma seleccionado.
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.
Prerequisites
- Back up your Satellite Server. For more information, see Backing Up Satellite Server and Capsule Server in Administering Red Hat Satellite.
3.1. Updating a disconnected Satellite Server on Red Hat Enterprise Linux 9 Copiar enlaceEnlace copiado en el portapapeles!
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
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.
-
List the repositories to identify their IDs:
$ hammer repository list \ --organization-label My_Organization_LabelExport the repositories in the syncable format:
$ hammer content-export complete repository \ --format syncable \ --id My_Repository_ID- Copy the exported directories to the disconnected Satellite Server.
Procedure on the disconnected Satellite Server
- Locate the copied exported directories.
Create the
/etc/yum.repos.d/update.repofile and update thebaseurlvalues 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/Upgrade
satellite-maintainto the next version:# satellite-maintain self-upgrade --maintenance-repo-label=satellite-maintenance-6.17-for-rhel-9-x86_64-rpmsEvaluate that the system is ready for update. The first time you run this command,
satellite-maintainprompts 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"- Review the results and resolve any errors before proceeding with the update.
Due to the lengthy update time, use a utility such as
tmuxto 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.logfile to confirm whether the process completed successfully.Perform the update:
# satellite-maintain update run --whitelist="repositories-validate,repositories-setup"If the satellite-maintain command told you to reboot, then reboot the system:
# reboot
Additional resources