Release Notes

Red Hat Update Infrastructure 3.1

Red Hat Customer Content Services


The Release Notes provide high-level coverage of the features and functionality that comprise Red Hat Update Infrastructure 3.1.

Chapter 1. Features

The Red Hat Update Infrastructure 3.1 features include:

  • two installation sources (RHUI packages in ISOs as well as in Red Hat CDN repositories) so you can choose how to install Red Hat Update Infrastructure.
  • easy installation using Puppet.
  • code rebased to Pulp 2.18 and MongoDB 2.6 to be consistent with the code base in Red Hat Satellite 6.
  • faster access to content due to reworked architecture for automated installations.
  • default use of Red Hat Gluster Storage as shared storage to speed up content availability at the content delivery server (CDS) and eliminate the need for synchronization.
  • high-availability deployment to reduce the error of one CDS not being synchronized with another CDS.
  • a load balancer/HAProxy node that is client-facing. (This functionality was integrated previously into the CDS logic.)
  • certificates managed by the rhui-installer and rhui-manager commands.
  • updates to yum.repos.d/*, certificates, and keys to use the new unified URL.
  • removal of client-side load balancing functionality from
  • support for Docker and OSTree (atomic) content.

See Chapter 16, Manage Certificates and Keys in the Red Hat Update Infrastructure System Administrator’s Guide for more details about Docker and OSTree content.

Chapter 2. Reworked architecture

2.1. Shared storage support

Red Hat Update Infrastructure 3.1 offers support for a shared storage volume for quicker availability of content to the clients. Red Hat Update Appliance and the CDSs are able to leverage the same storage location, which reduces synchronization times between the Red Hat Update Appliance and the CDSs.

2.2. NFS

With the option to use NFS, you can leverage your existing storage infrastructure to provide the storage for content.

2.3. Red Hat Gluster Storage

Red Hat Gluster Storage (formerly Red Hat Storage Server) provides redundant, scalable storage that can be installed on the same nodes (CDSs) running RHUI. This minimizes the number of nodes required for the deployment and ensures that there is no single point of failure in the deployment.

Red Hat Gluster Storage is an open, software-defined file storage that scales out as much as you need, and you can deploy the same storage on premises or in a public or hybrid cloud. Red Hat Gluster Storage provides new opportunities to unify data storage and infrastructure, increase performance, and improve availability and manageability to meet a broader set of an organization’s storage challenges and needs.

2.4. New installation process

Puppet drives the installation to configure all nodes in a single step. Certificates can be created by the installer. There is an HAProxy option to be able to load balance content requests for RPMs, OSTree content, and containers.

Report a bug

Chapter 3. Updates


Red Hat recommends that you back up your system before you perform any updates. Refer to the backup instructions in the Red Hat Update Infrastructure 3.1 System Administrator’s Guide for details on how to back up your system.


As of version 3.1, RHUI will not be supported on RHEL 6 anymore. This and future updates will only be made available for RHEL 7. Users of RHUI on RHEL 6 are encouraged to migrate to RHEL 7.

3.1. Updates for Red Hat Update Infrastructure 3.1.0

The MongoDB packages have been upgraded to upstream version 2.6, which provides a number of bug fixes and enhancements over the previous version. (BZ#1487523)

The Pulp packages have been upgraded to upstream version 2.18, which provides a number of bug fixes and enhancements over the previous version. The following list includes notable bug fixes:

  • When an updated version of updateinfo.xml.gz is found in Red Hat CDN, the previously saved updateinfo.xml.gz file is no longer kept locally in order to save disk space. Note that updateinfo.xml.gz files saved prior to this update will not be deleted after the next synchronization by Pulp 2.18. Remove them by hand or using the script described in the solution article which is linked in the References section. (BZ#1593218)
  • If an erratum affects multiple repositories, the updateinfo.xml.gz files are correctly generated for all of them so that the "yum updateinfo" command can correctly display the relevant errata information. (BZ#1599116)
  • The Red Hat Enterprise Linux 7 Server from RHUI repository has recently started to fail to synchronize, with an error message stating "DocumentTooLarge: BSON document too large." As a consequence, kernel-3.10.0-957.12.1.el7 was not available in RHUI. This problem has been fixed, and the repository can be synchronized correctly. (BZ#1707778)

This update adds the following enhancements:

  • As a Pulp-based solution, RHUI can serve as an alternate content source for another systems management product. A RHUI administrator can now create a configuration RPM containing files that allow the other product to download packages from RHUI. (BZ#1695464)
  • Legacy Certificate Authority (CA) certificates can be installed on CDS nodes to keep clients from losing access to entitled repositories after a new CA certificate is deployed in RHUI 3. (BZ#1698806)

3.2. Complete the update

Before applying this update, make sure all previously released errata relevant to your system have been applied.

For details on how to apply this update, refer to:


Before applying this update on CDS nodes, be sure to remount the shared filesystem, typically mounted at /var/lib/rhui/remote_share, read-write. This is necessary in order to allow the pulp-server package to update. Remount the filesystem read-only again after the update. Restart the httpd service in the end.


There are several steps to take after applying this update on the RHUA node:

  • Perform database migrations by running: sudo -u apache pulp-manage-db
  • Restart RHUI services by running: rhui-services-restart

Migrations may take several minutes to finish, depending on the number of repositories and packages you have in your RHUI. Be sure to pay attention to the output from the migrations. If you have RHEL 8 repositories in your RHUI, you may need to republish some of them. Follow the instructions in the output.

3.3. Updates for Red Hat Update Infrastructure 3.1.1

  • Previously, when a CDS node was unregistered from RHUI, it was not removed from HAProxy configuration. It is now removed from the configuration so that HAProxy does not keep track of the unregistered node anymore. (BZ#1454542)
  • Prior to this update, when a CDS or a HAProxy node was unregistered from RHUI using the command line, the relevant RHUI services, httpd and haproxy respectively, were not stopped on the nodes. In addition, the RHUI remote file system was left mounted on the unregistered CDS node. The command line interface was fixed to correctly clean up unregistered CDS or HAProxy nodes. (BZ#1640002)
  • Previously, only Red Hat repositories could be used when generating entitlement certificates on the command line. Any protected custom repositories also specified on the command line were ignored. With this update, protected custom repositories can be included when generating entitlement certificates on the command line. (BZ#1663422)

In addition, this update adds the following enhancements:

  • Client configuration RPMs can now be generated with custom proxy settings for Yum. The settings will be saved for each RHUI repository in the rh-cloud.repo file. Consult the RHUI 3.1 System Administrators Guide, linked to in the References section, for more information about this feature. (BZ#1658088)
  • When multiple repositories are scheduled to be synchronized, only a few of them can actually be actively synchronized at a time. The rest are waiting, but information about them is only kept in the system’s memory. If the system is rebooted or the Qpid service is restarted, the information about the repositories waiting for synchronization is lost. To allow the information to be saved on the disk, the Qpid persistence extension has been added. This feature is also described in the RHUI 3.1 System Administrators Guide. (BZ#1702254)
  • Client configuration RPMs used to be generated with a fixed release of "1". They can now be generated with any other release; the default release remains "1". This is useful if you have to generate a new configuration RPM containing updated certificates or repository data, and you do not want to use a higher version for any reason. (BZ#1715139)

Users of RHUI are advised to upgrade to these updated packages that fix these bugs and add these enhancements.

Chapter 4. Known issues

The known issues for Red Hat Update Infrastructure 3.1 includes the following subjects.

  1. When a user tries to list packages in repositories with a large amount of packages, rhui-manager reports an error:

    An unexpected error has occurred during the last operation. More information can be found in /root/.rhui/rhui.log.

    An example of a repository with a large amount of packages is Red Hat Enterprise Linux 7 Server from RHUI (RPMs) (7Server-x86_64). See BZ 1399605 for more details.

  2. A repository may not finish synchronizing if the Red Hat Update Appliance (RHUA) reboots while the task is running. If it becomes necessary to synchronize the repository manually, you should first check the task list in Pulp. Something internal in Pulp must have gone wrong, and you will need to cancel that task if it appears to be stuck in the Running state while nothing is actually being transferred. You can try synchronizing the affected repository in rhui-manager again. If the re-synchronization does not resolve the problem, you may have to cancel the new synchronization task, remove the broken repository, and add and synchronize the repository once more. See Check Repository Synchronization in the Red Hat Update Infrastructure System Administrator’s Guide for more details.
  3. When attempting to upload redhat-logos-4.9.16-1.noarch.rpm to a custom repository, the upload fails with the following error:

    An unexpected error has occurred during the last operation.
    More information can be found in /root/.rhui/rhui.log.

    See BZ#1198817 for more details.

  4. The user will not see an error message when the command-line interface (CLI) is used with invalid host names. See BZ#1409697 for more details.
  5. It is impossible to pull the OSTree repository on an Atomic Host immediately after it synchronizes for the first time. The synchronization must run at least twice; even then, the content is not available until Pulp publishes the files in the Apache directories, which takes several more minutes. Use the rhui-manager utility to forcibly run the synchronization for the second time or wait for the next synchronization, which occurs 4 hours after the first one. You can use the pulp-admin tasks list command on the RHUA node to check if a Pulp task is running and the pulp-admin tasks details --task-id ID command to check the progress of a running Pulp synchronization or publish task. See BZ#1427190 for more details.

Report a bug

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.