Upgrading connected Red Hat Satellite to 6.17

1. Ensure that your Satellite Servers and Capsule Servers have been upgraded to Satellite 6.16. For more information, see Upgrading connected Red Hat Satellite to 6.16 or Upgrading disconnected Red Hat Satellite to 6.16.

2. Upgrade your Satellite Server:

   1. Upgrade your Satellite Server to 6.17.
   2. Synchronize the new 6.17 repositories.

3. Upgrade your Capsule Servers:

   1. Upgrade all Capsule Servers to 6.17.

1. If you want to have several smaller outage windows instead of one larger window.
2. If Capsules in your organization are managed by several teams and are located in different locations.
3. If you use a load-balanced configuration, you can upgrade one load-balanced Capsule and keep other load-balanced Capsules at one version lower. This allows you to upgrade all Capsules one after another without any outage.

Upgrade Satellite Server

1. Stop all Satellite services:

   Copy to Clipboard Toggle word wrap

   # 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:

   Copy to Clipboard Toggle word wrap

   # 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:

   Copy to Clipboard Toggle word wrap

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

6. In the Satellite web UI, navigate to Hosts > Discovered hosts. On the Discovered Hosts page, power off and then delete the discovered hosts. From the Select an Organization menu, select each organization in turn and repeat the process to power off and delete the discovered hosts. Make a note to reboot these hosts when the upgrade is complete.

7. Ensure that the Satellite Maintenance repository is enabled:

   Copy to Clipboard Toggle word wrap

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

8. Upgrade satellite-maintain to its next version:

   Copy to Clipboard Toggle word wrap

   # satellite-maintain self-upgrade

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

   Copy to Clipboard Toggle word wrap

   # satellite-maintain upgrade check

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

10. Optional: 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/satellite.log file to check if the process completed successfully.

11. Perform the upgrade:

    Copy to Clipboard Toggle word wrap

    # satellite-maintain upgrade run

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

    Copy to Clipboard Toggle word wrap

    # reboot

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 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.17 (for RHEL 9 x86_64) (RPMs)

     Red Hat Satellite Maintenance 6.17 (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)

   Note

   If the 6.17 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.17. Note that Red Hat Satellite Client 6 does not have a 6.17 version. Choose 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:

   Copy to Clipboard Toggle word wrap

   # yum clean metadata

3. Synchronize the satellite-capsule-6.17-for-rhel-9-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. Optional: 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.

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

   Ensure that the Satellite Maintenance repository is enabled:

   Copy to Clipboard Toggle word wrap

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

   Ensure Capsule has access to satellite-maintenance-6.17-for-rhel-9-x86_64-rpms and execute:

   Copy to Clipboard Toggle word wrap

   # satellite-maintain self-upgrade

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

   Copy to Clipboard Toggle word wrap

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

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

   Copy to Clipboard Toggle word wrap

   # satellite-maintain upgrade check

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

9. Perform the upgrade:

   Copy to Clipboard Toggle word wrap

   # satellite-maintain upgrade run

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

    Copy to Clipboard Toggle word wrap

    # reboot

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

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. Update permissions to prepare the postgresql-evr extension for removal:

   Copy to Clipboard Toggle word wrap

   # runuser -l postgres -c \
   "psql -d foreman -c \"UPDATE pg_extension SET extowner = (SELECT oid FROM pg_authid WHERE rolname='foreman') WHERE extname='evr';\""

2. Follow Section 2.2, “Upgrading a connected Satellite Server”.

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:

   Copy to Clipboard Toggle word wrap

   # 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, no further changes are required. Otherwise, reconfigure Satellite to use the new name:

   Copy to Clipboard Toggle word wrap

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