ApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 5. 4.2 Release Notes

5.1. New Features

This following major enhancements have been introduced in Red Hat Update Infrastructure 4.2.

Importing package group metadata to a custom repository is now supported
With this update, data from a comps file can now be imported and included into the metadata for a custom repository. For more information, see Importing package group metadata to a custom repository.
Faster package uploads
Previously, rhui-manager uploaded a single package at a time and republished the custom repository after each upload. With this update, rhui-manager creates a temporary repository instead, which contains all the packages that have to be uploaded. Additionally, rhui-manager also creates the repodata for this temporary repository. To upload the packages to the custom repository, rhui-manager synchronizes the custom repository with the temporary one. As a result, package uploads are now significantly faster.
User supplied HAProxy configuration file is now supported
With this update, you can specify a custom template for an HAProxy configuration when adding an HAProxy load balancer to your RHUI instance. If you do not specify a custom file, the default template is used. The default template is stored in the /usr/share/rhui-tools/templates/haproxy.cfg file.
New rhui-manager aliases
With this update, aliases for the --username and --password options for the rhui-manager command are now supported in the command-line interface. You can now use the short forms -u and -p respectively.
gunicorn services now restart automatically
With this update, gunicorn services restart automatically if they exit unexpectedly. As a result, CDS nodes can now recover from situations where these services stop unexpectedly, for example, when the system runs out of memory.
Upgraded rhui-manager utility

With this update, the following new option and flag are now available in rhui-manager:

  • repo add_by_file option to add repositories using a YAML input file. For more information, see Adding a new Red Hat content repository using an input file.
  • --sync_now flag to sync any repositories that are added. This flag is now available with the rhui-manager repo add_by_repo and rhui-manager repo add_by_file commands.

5.2. Bug Fixes

The following bugs have been fixed in Red Hat Update Infrastructure 4.2 that have a significant impact on users.

Migrating to a different remote file server now works as expected
Previously, when rhui-installer was rerun with a remote file server, which was different from the one that was originally used, rhui-installer failed to unmount the original file server. Additionally, rhui-installer also failed to remove the record of the file server from the /etc/fstab file. Consequently, migrating to another remote file server failed. With this update, rhui-installer successfully unmounts the remote file server and also removes its record. As a result, migrating to a different remote file server now works as expected.

5.3. Known Issues

This part describes known issues in Red Hat Update Infrastructure 4.2.

Repository synchronization tasks fail when updating Red Hat Update Infrastructure

When you update RHUI, Pulp worker processes are shut down and restarted once the update is complete. Consequently, any repository synchronization tasks that are scheduled during the update might be aborted with the following error: 

Aborted during worker shutdown

As a workaround, aborted repository synchronization tasks are automatically rerun at the next available time slot. The default is 6 hours. Alternatively, you can manually synchronize repositories after the update is complete.

rhui-installer ignores custom RHUI CA when updating to a newer version of RHUI

When updating from RHUI version 4.1.0 or older, rhui-installer ignores the existing custom RHUI CA and generates a new RHUI CA regardless of the parameter value set in the answer.yml file. Consequently, RHUI fails to recognize clients which use the older RHUI CA. To work around this problem, specify the custom RHUI CA when running the rhui-installer --rerun command. 

# rhui-installer --rerun --user-supplied-rhui-ca-crt <custom_RHUI_CA.crt> --user-supplied-rhui-ca-key <custom_RHUI_CA_key>

For more information, see Updating Red Hat Update Infrastructure.

rhui-manager repo unused command fails to list newly added repositories

Currently, the rhui-manager repo unused command displays all the repositories that are listed in the entitlement certificate but are not used by RHUI. However, when new repositories are added to the certificate, they might not be immediately available to the RHUA node due to a previously active denylist. Consequently, they are not displayed when you run the command to list the unused repositories. To work around this problem, you must remove the repository cache. You can do so by running the following command: 

# rm -f /var/cache/rhui/*
Red Hat logoGithubRedditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

© 2024 Red Hat, Inc.