Chapter 2. Upgrading Red Hat Satellite

Upgrade disconnected Satellite Server

1. Stop all Satellite services:

   # satellite-maintain service stop

2. Take a snapshot or create a backup:

   • On a virtual machine, take a snapshot.
   • On a physical machine, create a backup.

3. Start all Satellite services:

   # satellite-maintain service start

4. Optional: If you made manual edits to DNS or DHCP configuration in the /etc/zones.conf or /etc/dhcp/dhcpd.conf files, back up the configuration files because the installer only supports one domain or subnet, and therefore restoring changes from these backups might be required.

5. Optional: If you made manual edits to DNS or DHCP configuration files and do not want to overwrite the changes, enter the following command:

   # satellite-installer --foreman-proxy-dns-managed=false \
   --foreman-proxy-dhcp-managed=false

6. In the Satellite web UI, navigate to Hosts > Discovered hosts. If there are discovered hosts available, turn them off and then delete all entries under the Discovered hosts page. Select all other organizations in turn using the organization setting menu and repeat this action as required. Reboot these hosts after the upgrade has completed.

7. Remove old repositories:

   # rm /etc/yum.repos.d/*

8. Obtain the latest ISO files by following the Downloading the Binary DVD Images procedure in Installing Satellite Server in a disconnected network environment.

9. Create directories to serve as a mount point, mount the ISO images, and configure the rhel8 repository by following the Configuring the Base Operating System with Offline Repositories in RHEL 8 procedure in Installing Satellite Server in a disconnected network environment.

   Do not install or update any packages at this stage.

10. Configure the Satellite 6.15 repository from the ISO file.

    1. Copy the ISO file’s repository data file for the Red Hat Satellite packages:

       # cp /media/sat6/Satellite/media.repo /etc/yum.repos.d/satellite.repo

    2. Edit the /etc/yum.repos.d/satellite.repo file:

       # vi /etc/yum.repos.d/satellite.repo

       1. Change the default InstallMedia repository name to Satellite-6.15:

          [Satellite-6.15]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/Satellite

11. Configure the Red Hat Satellite Maintenance repository from the ISO file.

    1. Copy the ISO file’s repository data file for Red Hat Satellite Maintenance packages:

       # cp /media/sat6/Maintenance/media.repo /etc/yum.repos.d/satellite-maintenance.repo

    2. Edit the /etc/yum.repos.d/satellite-maintenance.repo file:

       # vi /etc/yum.repos.d/satellite-maintenance.repo

       1. Change the default InstallMedia repository name to Satellite-Maintenance:

          [Satellite-Maintenance]

       2. Add the baseurl directive:

          baseurl=file:///media/sat6/Maintenance/

12. Enable the maintenance module:

    # dnf module enable satellite-maintenance:el8

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

    If you lose connection to the command shell where the upgrade command is running you can see the logs in /var/log/foreman-installer/satellite.log to check if the process completed successfully.

14. Check the available versions to confirm the version you want is listed:

    # satellite-maintain upgrade list-versions

15. Use the health check option to determine if the system is ready for upgrade. When prompted, enter the hammer admin user credentials to configure satellite-maintain with hammer credentials. These changes are applied to the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

    # satellite-maintain upgrade check --target-version 6.15 \
    --whitelist="repositories-validate,repositories-setup"

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

16. Perform the upgrade:

    # satellite-maintain upgrade run --target-version 6.15 \
    --whitelist="repositories-validate,repositories-setup"

    If the script fails due to missing or outdated packages, you must download and install these separately. For more information, see Resolving Package Dependency Errors in Installing Satellite Server in a disconnected network environment.

17. Determine if the system needs a reboot:

    # dnf needs-restarting --reboothint

18. If the previous command told you to reboot, then reboot the system:

    # reboot

19. Optional: If you made manual edits to DNS or DHCP configuration files, check and restore any changes required to the DNS and DHCP configuration files using the backups that you made.

20. If you make changes in the previous step, restart Satellite services:

    # satellite-maintain service restart

21. If you have the OpenSCAP plugin installed, but do not have the default OpenSCAP content available, enter the following command.

    # foreman-rake foreman_openscap:bulk_upload:default

22. In the Satellite web UI, navigate to Configure > Discovery Rules.
23. Associate selected organizations and locations with discovery rules.

Procedure

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.
2. Toggle the Recommended Repositories switch to the On position.

3. From the list of results, expand the following repositories and click the Enable icon to enable the repositories:

   • To upgrade Satellite clients, enable the Red Hat Red Hat Satellite Client 6 repositories for all Red Hat Enterprise Linux versions that clients use.

   • If you have Capsule Servers, to upgrade them, enable the following repositories too:

     Red Hat Satellite Capsule 6.15 (for RHEL 8 x86_64) (RPMs)

     Red Hat Satellite Maintenance 6.15 (for RHEL 8 x86_64) (RPMs)

     Red Hat Enterprise Linux 8 (for x86_64 – BaseOS) (RPMs)

     Red Hat Enterprise Linux 8 (for x86_64 – AppStream) (RPMs)

   Note

   If the 6.15 repositories are not available, refresh the Red Hat Subscription Manifest. In the Satellite web UI, navigate to Content > Subscriptions, click Manage Manifest, then click Refresh.

4. In the Satellite web UI, navigate to Content > Sync Status.
5. Click the arrow next to the product to view the available repositories.
6. Select the repositories for 6.15. Note that Red Hat Red Hat Satellite Client 6 does not have a 6.15 version. Choose Red Hat Red Hat Satellite Client 6 instead.

7. Click Synchronize Now.

   Important

   If an error occurs when you try to synchronize a repository, refresh the manifest. If the problem persists, raise a support request. Do not delete the manifest from the Customer Portal or in the Satellite web UI; this removes all the entitlements of your content hosts.

8. If you use content views to control updates to the base operating system of Capsule Server, update those content views with new repositories, publish, and promote their updated versions. For more information, see Managing content views in Managing content.

Upgrading Capsule Servers

1. Create a backup.

   • On a virtual machine, take a snapshot.

   • On a physical machine, create a backup.

     For information on backups, see Backing Up Satellite Server and Capsule Server in Administering Red Hat Satellite.

2. Clean yum cache:

   # yum clean metadata

3. Synchronize the satellite-capsule-6.15-for-rhel-8-x86_64-rpms repository in the Satellite Server.
4. Publish and promote a new version of the content view with which the Capsule is registered.

5. The rubygem-foreman_maintain is installed from the Satellite Maintenance repository or upgraded from the Satellite Maintenance repository if currently installed.

   Ensure Capsule has access to satellite-maintenance-6.15-for-rhel-8-x86_64-rpms and execute:

   # satellite-maintain self-upgrade

6. On Capsule Server, verify that the foreman_url setting points to the Satellite FQDN:

   # grep foreman_url /etc/foreman-proxy/settings.yml

7. Check the available versions to confirm the version you want is listed:

   # satellite-maintain upgrade list-versions

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

   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/capsule.log file to check if the process completed successfully.

9. Use the health check option to determine if the system is ready for upgrade:

   # satellite-maintain upgrade check --target-version 6.15

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

10. Perform the upgrade:

    # satellite-maintain upgrade run --target-version 6.15

11. Determine if the system needs a reboot:

    # dnf needs-restarting --reboothint

12. If the previous command told you to reboot, then reboot the system:

    # reboot

13. Optional: If you made manual edits to DNS or DHCP configuration files, check and restore any changes required to the DNS and DHCP configuration files using the backups made earlier.
14. Optional: If you use custom repositories, ensure that you enable these custom repositories after the upgrade completes.

Upgrading Capsule Servers using remote execution

1. Create a backup or take a snapshot.

   For more information on backups, see Backing Up Satellite Server and Capsule Server in Administering Red Hat Satellite.

2. In the Satellite web UI, navigate to Monitor > Jobs.
3. Click Run Job.
4. From the Job category list, select Maintenance Operations.
5. From the Job template list, select Capsule Upgrade Playbook.
6. In the Search Query field, enter the host name of the Capsule.
7. Ensure that Apply to 1 host is displayed in the Resolves to field.
8. In the target_version field, enter the target version of the Capsule.
9. In the whitelist_options field, enter the options.
10. Select the schedule for the job execution in Schedule.
11. In the Type of query section, click Static Query.

Procedure

1. Create a backup.
2. Restore the backup on the new server.

3. If Satellite reaches the new database server via the old name, no further changes are required. Otherwise reconfigure Satellite to use the new name:

   # satellite-installer \
   --foreman-db-host newpostgres.example.com \
   --katello-candlepin-db-host newpostgres.example.com \
   --foreman-proxy-content-pulpcore-postgresql-host newpostgres.example.com