Chapter 2. Upgrading Red Hat Update Infrastructure Red Hat Update Infrastructure (RHUI) is periodically upgraded to introduce bug fixes, enhancements, and fix common vulnerabilities and exposures. Important Red Hat recommends keeping your installation up to date by applying the latest RHUI updates when they are released. 2.1. Updating Red Hat Update Infrastructure To update your instance of Red Hat Update Infrastructure (RHUI) to the latest version, you must take the following steps. Prerequisites Root access to the RHUA node. All of your RHUI nodes are subscribed and are using the correct repositories as desribed in Installing Red Hat Update Infrastructure . Repository synchronization tasks are scheduled to run after the update is complete. Tasks that run while the update is in progress might be aborted. For more information see Known Issues . Important The rhui-installer supports upgrading the version of PostgreSQL. Before doing that it is important to back up your PostgreSQL database. How to back up your PostgreSQL database is described in Chapter 12. Backing up and restoring Red Hat Update Infrastructure of the Configuring and Managing Red Hat Update Infrastructure documentation. Important Do not attempt to keep the RHUA node up to date by simply applying all available package updates. Doing so may break the RHUA. Updating the RHUA must be performed exclusively by following the procedure below. If you only want to apply OS updates and exclude any RHUI package updates, exclude the RHUI repository in your update transaction. For example, on the command line, run the following command: You may need to reboot the system or restart RHUI services after this transaction. Note To keep the CDS nodes up to date, it is not sufficient to apply available package updates on them. Because various configurations are modified in many RHUI versions, it is necessary to reapply the configurations by following the procedure below. Procedure On the RHUA node, update RHUI Installer. Run RHUI Installer: If you are updating from RHUI 4.10 and you have already started using the on_demand synchronization policy, copy the relevant part of the configuration to the custom configuration file as described in Preserving Custom Configuration After RHUI Upgrade . Run the rhui-installer command as follows: If you are updating from RHUI 4.1.0 or older, you must specify your custom RHUI CA along with the rerun option: If you are updating from RHUI 4.1.1 or newer, run RHUI Installer with just the rerun option: If you are updating the version of PostgreSQL from 12 to 15 you must specify this using the --postgresql-version option along with the rerun option: Optional: In some environments, rhui-installer fails to rerun and displays the following error instead: To fix this error: Run the following command on the RHUA node: Run rhui-installer with the rerun option. Check if the rhui-installer installed updated packages. By default the rhui-installer will install any available RHEL package updates. RHUA must be rebooted if any package has been updated that requires rebooting. The command to check this is: Note This command is part of the yum-utils package, which must be installed on the RHUA for the command to be available. To apply updated templates and playbooks, reinstall all of the CDS nodes. This will also install any available RHEL package updates. To avoid that, run the below command with the --no_update flag. Check if updated packages were installed on the CDS nodes. If package updates were installed the CDS nodes may need to be rebooted. To check if your CDS nodes do need to be rebooted, log on to them and run this command: Note This command is part of the yum-utils package, which must be installed on the CDS for the command to be available. Log in to RHUI Manager. Verification On the RHUA node, run the following command and verify whether the latest version of RHUI is installed.

Commands:
dnf --disablerepo=rhui-4-for-rhel-8-x86_64-rpms update
dnf update rhui-installer
rhui-installer --rerun --user-supplied-rhui-ca-crt <custom_RHUI_CA.crt> --user-supplied-rhui-ca-key <custom_RHUI_CA_key>
rhui-installer --rerun
rhui-installer --postgresql-version 15 --rerun
There have been identified artifacts with forbidden checksum md5 . Run pulpcore-manager handle-artifact-checksums first to unset forbidden checksums.
env PULP_SETTINGS=/etc/pulp/settings.py pulpcore-manager handle-artifact-checksums
needs-restarting -r
rhui-manager --noninteractive cds reinstall --all
needs-restarting -r
rhui-manager
rpm -q rhui-tools