Chapter 6. 4.3 Release Notes
6.1. New Features
This following major enhancements have been introduced in Red Hat Update Infrastructure 4.3.
- New Pulp version:
3.21.0
-
This update introduces a newer version of Pulp,
3.21.0
. Among other upstream bug fixes and enhancements, this version changes how Pulp manages ambiguous CDN repodata that contains a duplicate packagename-version-release
string. Instead of failing, Pulp logs a warning and allows the affected repository to be synchronized. - New
rhui-manager
command A new
rhui-manager
command is now available:`rhui-manager [--noninteractive] cds reinstall --all`
With this command, you can reinstall all of your CDS nodes using a single command. Additionally, you do not need to specify any of the CDS host names.
6.2. Bug Fixes
The following bugs have been fixed in Red Hat Update Infrastructure 4.3 that have a significant impact on users.
- Alternate Content Source package can now be created
-
Previously,
rhui-manager
failed to create an Alternate Content Source package. With this update, the problem is now fixed and you can successfully create an Alternate Content Source package. - Redundant RHUI code has now been removed
-
With this update, several parts of redundant code have been removed from RHUI. Most notably, the unused
entitlement
argument in the custom repository creation has been removed. Additionally, the Atomic and OSTree functions have been removed because these features have been deprecated in RHUI 4. port
variable has been renamed toremote_port
-
Previously, CDS and HAProxy management used a variable called
port
. However,port
is a reserved playbook keyword in Ansible. Consequently, Ansible printed warnings about the use of this variable. With this update, the variable has been renamed toremote_port
which prevents the warnings. rhui-installer
now returns the correct status when RHUA installation playbooks fails-
Previously, when the RHUA installation playbook failed,
rhui-installer
exited with a status of0
, which normally indicates success. With this update, the problem has been fixed, andrhui-installer
exits with a status of1
, indicating that the RHUA installation playbook has failed. - Proxy-enabled RHUI environments can now synchronize container images
- Previously, RHUI did not accept proxy server settings when adding container images. Consequently, RHUI was unable to synchronize container images if the proxy server configuration was required to access the container registries. With this update, RHUI now accepts proxy settings when they are configured with the container images. As a result, proxy-enabled RHUI environments can now synchronize container images.
- Misaligned text on the repository workflow screen is now fixed
- With this update, the misaligned text on the repository workflow screen in the rhui-manager text interface has been fixed.
6.3. Known Issues
This part describes known issues in Red Hat Update Infrastructure 4.3.
- Rerunning
rhui-installer
resets custom container configuration -
Currently, the container configuration registry is managed by editing the
rhui-tools.conf
configuration file. However, rerunningrhui-installer
overwrites the configuration file based on the latest answers file or based on the command line parameters combined with the default template, which doesn’t contain any container registry configuration. Consequently, rerunningrhui-installer
resets any custom changes to the container configuration registry. To work around this problem, save the current container configuration section from the/etc/rhui/rhui-tools.conf
file and reapply the configuration to the newrhui-tools.conf
file that is generated after rerunningrhui-installer
.