Chapter 1. What’s New


Red Hat Update Infrastructure 5.1 March 2026

The following enhancements are now available in RHUI 5:

  • RHUI has a new CLI capability that validates repository content is actually up to date with the Red Hat CDN, not only that sync has completed. This addresses cases where a RHUI instance reported successful sync but was still serving outdated content (such as missing critical updates). This enhancement includes:

    • A CLI command to validate repo freshness against the Red Hat CDN and surface discrepancies when a repo appears synced but lacks the latest updates.
    • Validation of kernel version freshness across five kernel versions to make it easier to spot outdated content.
    • Detection and reporting of misconfiguration that can lead to outdated content, with a clearer “freshness” measure for diagnostics.
  • Logging is no longer hardcoded in the CLI. A new [logging] section allows configuration of:

    • max_bytes and backupCount for the rotating log file (defaults increased to 3 MB and 6 rotated log files).
    • log_level (moved into the logging section).
    • cleanup_type as a strategy for the rotation, which can be based on either the number or the age of the logs
    • max_age to set how long the logs should be kept when using the age-based cleanup type

      The codebase was updated so log path and filename are read from configuration instead of being hardcoded where applicable (with consideration for tools like the sos rhui plugin that expect a known location). See /etc/rhui-static/rhui-tools-static.conf in the RHUA container for details and default values. To set custom values, edit the /etc/rhui/rhui-tools.conf file.

  • RHUI now converts the original cron jobs to systemd timers and adds randomized delay so each RHUA does not run tasks at the same clock minute to address potential release spikes on the CDN.

The following bug fixes are now available in RHUI 5:

  • Previously older RHUI installations were retaining significantly more on-disk data than newer ones because old repository metadata was not removed. This fix introduces cleanup of obsolete repo metadata so storage growth from unused metadata is reduced.
  • Previously under certain boot conditions, the RHUA or CDS container would fail to start because the NFS mount for /var/lib/rhui/remote_share was not ready when the service started, leading to a dependency failure that generated such error messages as “Failed to mount /var/lib/rhui/remote_share”, or “Dependency failed for RHUI CDS”. The fix ensures the RHUA and CDS containers will start reliably even when the remote share becomes available slightly later after boot.
  • Previously migration of a RHUA that had a CDS node and used auth.json for registry authentication could fail during the “Inject container registry info into instance data” Ansible step with an error about a missing rhua_container_registry attribute on the instance data. This issue has been fixed.
  • Previously when using the installer with a Podman or RHUI RHUI administrator password that contained characters reserved in YAML, the password was passed directly into the playbook. This led to YAML parsing errors such as “exception occurred during task execution” or “Convert install_params_str to a dictionary”. This release corrects password handling in the installer playbook so special characters no longer cause installer failures.

Red Hat Update Infrastructure 5.0 November 2025
  • RHUI 5 has been completely redesigned to run as containers. This means each part of the system — from syncing content to delivering updates — is packaged into containers. All appliances and the installer are delivered as container images which means that RHUI 5 can be run on RHEL and later versions, Fedora, and other platforms that support podman and can be provisioned via Red Hat Ansible Automation Platform.
  • RHUI 5 containers are rootless.
  • Migrating to RHUI 5 can be performed in both in-place and hybrid mode. Hybrid mode means that the target RHUI 5 machine could have a different operating system or version.
  • RHUI 5 installation can now be cloned

The following issues that were reported in RHUI 4 are resolved in Red Hat Update Infrastructure5:

  • The rhui-installer can now manage max-requests values for Gunicorn.
  • Gunicorn logs are now located in /var/log/pulp.
  • A cron job has been added to clean up Pulp’s temp files.
  • The rhui-manager now supports stop-syncing.
  • RHSM Entitlement certification can now be verified by hash.

The following enhancements are now available in RHUI 5.

  • When the content delivery system (CDS) is re-installed, RHUI will automatically check for refreshed certificates.
  • RHUI 5 now supports passwordless local connections via Unix sockets.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red Hat
Back to top