Chapter 4. Known issues

The known issues for Red Hat Update Infrastructure 3.1.9 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. 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