Este contenido no está disponible en el idioma seleccionado.
Chapter 8. 4.5 Release Notes
8.1. New Features
This following major enhancements have been introduced in Red Hat Update Infrastructure 4.5.
yum
plugins are no longer automatically enabled-
With this update, the client configuration RPMs in
rhui-manager
prevent subscription manager from automatically enablingyum
plugins. As a result, RHUI repository users will no longer see irrelevant messages from subscription manager. - RHUI repository status files are now machine-readable
With this update, you can generate machine-readable files with the status of each RHUI repository. To use this feature, run the following command:
rhui-manager --non-interactive status --repo_json <output file>
- Exit codes are now available with
rhui-manager
With this update, the
rhui-manager
CLI command uses a variety of unique exit codes to indicate different types of errors. For example, if you attempt to add a Red Hat repository that has already been added, the command will exit with a status of245
. However, if you attempt to add a Red Hat repository that does not exist in the RHUI entitlement, the command will exit with a status of246
.For a complete list of codes, see the
/usr/lib/python3.6/site-packages/rhui/common/rhui_exit_codes.py
file.
8.2. Bug Fixes
The following bugs have been fixed in Red Hat Update Infrastructure 4.5 that have a significant impact on users.
- Using a cron job to run
rhui-manager
no longer generates a login name error message -
Previously, the
rhui-manager
command used thelogname
command to obtain the login name. However, whenrhui-manager
is run using therhui-repo-sync
cron job, a login name is not defined. Consequently, emails sent by the cron job contained the error messagelogname: no login name
. With this update,rhui-manager
does not obtain the login name using thelogname
command and the error message is no longer generated. rhui-manager
no longer logs a traceback when an invalid repository ID is usedPreviously, when an invalid repository ID was used with the
rhui-manager
command to synchronize or delete a repository, the command failed with following error:An unexpected error has occurred during the last operation.
Additionally, a traceback was also logged.
With this update, the error message has been improved and failure to run no longer logs a traceback.
8.3. Known Issues
This part describes known issues in Red Hat Update Infrastructure 4.5.
- Upgrading to RHUI 4.5 fails due to active logins
Currently, when you try to upgrade RHUI instances that were deployed before RHEL 8.6, which run Ansible Engine rather than Ansible Core, the installer fails with the following error:
RUNNING HANDLER [Delete the active login session file] *********************************************************************** [DEPRECATION WARNING]: evaluating 'rhui_active_login_file' as a bare variable, this behaviour will go away and you might need to add |bool to the expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle. This feature will be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. fatal: [localhost]: FAILED! => {"msg": "The conditional check 'rhui_active_login_file' failed. The error was: template error while templating string: unexpected '/'. String: {% if /root/.rhui/http-localhost:24817 %} True {% else %} False {% endif %}\n\nThe error appears to be in '/usr/share/rhui-installer/playbooks/rhua-provision.yml': line 76, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - name: Delete the active login session file\n ^ here\n"}
To work around this problem, remove the current active logins using the
rhui-manager --logout
command and then run therhui-installer --rerun
command again.