Chapter 3. Upgrading Red Hat Satellite

Procedure

1. Create a backup of your 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

2. Remove old repositories:

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

3. Export the required repositories from your connected Satellite Server to your disconnected Satellite Server:

   1. Ensure that your connected server synchronizes the following repositories with the download policy set to Immediate:

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

   2. List the repositories to identify their IDs:

      $ hammer repository list \
      --organization-label My_Organization_Label

   3. Export each repository in the syncable format by using its repository ID:

      $ hammer content-export complete repository \
      --format syncable \
      --id My_Repository_ID

   4. Copy the exported directories to the disconnected Satellite Server.

4. On the disconnected server, enable access to the exported content by configuring a repository:

   1. Locate the copied directories from the syncable export.

   2. Create the /etc/yum.repos.d/upgrade.repo file and update the baseurl directive to point to that location:

      [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.19-for-rhel-9-x86_64-rpms]
      name=Red Hat Satellite 6.19 for RHEL 9 Server RPMs x86_64
      enabled=0
      metadata_expire=-1
      gpgcheck=0
      baseurl=file:///Satellite_Export_Location/content/dist/layered/rhel9/x86_64/satellite/6.19/os/
      
      [satellite-maintenance-6.19-for-rhel-9-x86_64-rpms]
      name=Red Hat Satellite Maintenance 6.19 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.19/os/

      Keep the satellite-6.19-for-rhel-9-x86_64-rpms repository disabled.

5. Upgrade the satellite-maintain utility to its latest version:

   # satellite-maintain self-upgrade --maintenance-repo-label=satellite-maintenance-6.19-for-rhel-9-x86_64-rpms

6. Check whether your system is ready for Satellite upgrade:

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

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

   Note

   The satellite-maintain upgrade check might prompt you for the Hammer admin user credentials. It applies changes to the /etc/foreman-maintain/foreman-maintain-hammer.yml file.

7. Edit the /etc/yum.repos.d/upgrade.repo file and enable the satellite-6.19-for-rhel-9-x86_64-rpms repository:

   [satellite-6.19-for-rhel-9-x86_64-rpms]
   name=Red Hat Satellite 6.19 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.19/os/

8. Run the Satellite Server upgrade command. Because of the lengthy upgrade time, consider using a utility such as tmux. For more information, see Section 2.3, “Following the progress of the upgrade”.

   # satellite-maintain upgrade run --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.

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

   # reboot

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

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

12. Perform the following post-upgrade tasks to ensure your environment is adjusted to any changes applied during the upgrade.

    1. If you use Red Hat Lightspeed in Satellite, update the Common Vulnerabilities and Exposures (CVE) vulnerability mapping file:

       • On a connected system, download the latest cvemap.xml file from the Red Hat Customer Portal:

         $ curl \
         --output /var/www/html/pub/cvemap.xml \
         https://security.access.redhat.com/data/meta/v1/cvemap.xml

       • Transfer cvemap.xml to the disconnected Satellite Server you are upgrading, and place it in /var/lib/foreman/.

         Satellite detects the new file and publishes it to the internal Red Hat Lightspeed in Satellite services.

    2. Verify whether the default templates changed during the upgrade. Update any custom templates that you created by cloning a default template to reflect these changes.

       Note

       Use custom provisioning snippets to execute custom code before or after the provisioning process instead of cloning default templates. You can avoid recreating cloned templates if you use custom provisioning snippets. For more information about configuring custom provisioning snippets, see Running custom code during host provisioning by using Satellite web UI in Provisioning hosts.

    3. If your Satellite shows any discovered hosts, reboot them:

       1. In the Satellite web UI, navigate to Hosts > Discovered hosts.
       2. Select Any Organization to display all discovered hosts.
       3. Reboot all discovered hosts.

Procedure

1. In the Satellite web UI, navigate to Content > Red Hat Repositories.

2. Enable the following repositories:

   • Repositories required to upgrade Capsule Servers:

     • Red Hat Satellite Capsule 6.19 (for RHEL 9 x86_64) (RPMs)
     • Red Hat Satellite Maintenance 6.19 (for RHEL 9 x86_64) (RPMs)
     • Red Hat Enterprise Linux 9 (for x86_64 – BaseOS) (RPMs)
     • Red Hat Enterprise Linux 9 (for x86_64 – AppStream) (RPMs)

   • Repositories required to upgrade Satellite clients:

     • Red Hat Satellite Client 6 for each Red Hat Enterprise Linux version your clients are using
     • If you use Puppet to manage host configurations, Red Hat Satellite Client 6 OpenVox for each Red Hat Enterprise Linux version your clients are using
3. In the Satellite web UI, navigate to Content > Sync Status.

4. Synchronize the following repositories:

   • All repositories for version 6.19
   • Red Hat Satellite Client 6 repositories for each Red Hat Enterprise Linux version your clients are using
5. If you use Puppet to manage host configurations, manually update the content views for your hosts. Add the Red Hat Satellite Client 6 OpenVox repository for the Red Hat Enterprise Linux version your clients are using to the content views and publish and promote a new version of the content views.

Procedure

1. Create a backup of your Capsule Server. The backup can be a virtual machine (VM) snapshot or a regular full backup. For more information, see Backing up Satellite Server and Capsule Server in Administering Red Hat Satellite.

2. Ensure that the Satellite Maintenance repository is enabled:

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

3. Upgrade the satellite-maintain utility on the Capsule Server to its latest version:

   # satellite-maintain self-upgrade

4. Determine whether Capsule Server is ready for the upgrade:

   # satellite-maintain upgrade check

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

5. Run the Satellite upgrade command. Because of the lengthy upgrade time, consider using a utility such as tmux. For more information, see Section 2.3, “Following the progress of the upgrade”.

   # satellite-maintain upgrade run

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

   # reboot

Procedure

1. Create a backup of your existing external database.
2. Restore the backup on the new Red Hat Enterprise Linux 9 server.

3. Verify that Satellite can reach the new database:

   # PGPASSWORD='My_Foreman_Database_Password' psql -h postgres.example.com -p 5432 -U foreman -d foreman -c "SELECT 1 as ping"

4. If your Satellite Server can reach the new database server by using the old name, you do not need to make any further changes. 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