Release Notes

Using rhui-manager to create an alternate source client configuration repository fails with the following error:

No usable repository found, not building the RPM.

No usable repository found, not building the RPM.

There is no workaround available at the moment

With this update, containers are now supported on RHUI.

You can now perform the following operations:

With this update, you can specify the following certificates and keys during RHUI installation:

Previously, when a path for a non-RHUI repository was used in the entitlement certificate, RHUI Manager logged the following error message in the /var/log/messages file:

...
Invalid entitlement path %s found
...

...
Invalid entitlement path %s found
...

With this update, the error message has been clarified and reworded to the following message:

...
Invalid repository download URL: %s provided
...

...
Invalid repository download URL: %s provided
...

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>

# 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.

Previously, when you reran an instance of RHUI Installer which was not up-to-date, RHUI Installer updated the RHUI packages if newer versions were available. As a result, the RHUI system would enter an inconsistent state since the older version of the RHUI Installer package was not aware of potential changes to the RHUI package set.

In addition, running RHUI Installer to change a setting, without updating RHUI in the process, was not supported.

With this update, when you rerun RHUI Installer, it checks whether a newer version is available. If available, RHUI Installer displays an error message stating that you must either update the RHUI Installer package, or rerun the RHUI Installer command using the --ignore-newer-rhui-packages argument. The --ignore-newer-rhui-packages argument prevents the installer from applying any RHUI updates.

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>

# 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.

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

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

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.

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>

# 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.

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/*

# rm -f /var/cache/rhui/*

A new rhui-manager command is now available:

`rhui-manager [--noninteractive] cds reinstall --all`

`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.

With this update, Content Delivery Server (CDS) nodes can now be configured to never fetch unexported content from the RHUA node. To use this feature, re-run the rhui-installer command with the --fetch-missing-symlinks False argument, and reapply the configuration to all CDS nodes by running the rhui-manager cds reinstall --all command.

If you configure your CDS nodes this way, ensure you export the content before RHUI clients start consuming it. By default, cron jobs running regularly on the RHUA node export content automatically. However, you can manually export the content by running the rhui-manager repo export --repo_id REPOSITORY_ID command.

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>

rhui-manager --non-interactive status --repo_json <output file>

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 of 245. 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 of 246.

For a complete list of codes, see the /usr/lib/python3.6/site-packages/rhui/common/rhui_exit_codes.py file.

Previously, 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.

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.

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"}

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 the rhui-installer --rerun command again.

It is now possible to set the synchronization of RPM, Source, and Debug repositories separately as either 'immediate' or 'on-demand'.

When 'on-demand' is selected, content is downloaded only when requested by the end client. This option is generally useful for source and debug content, as they are not widely used. As a result, the amount of content stored by RHUI can drop significantly.

You can configure this in /etc/rhui/rhui-tools.conf. The mandatory option is to set the default_sync_policy to either 'immediate' or 'on-demand'. Optionally, you can override this setting by specifying rpm_sync_policy, source_sync_policy, and/or debug_sync_policy.

Currently, when you reinstall RHUI with a new Certificate Authority (CA) and then you want to reinstall CDS nodes to use the new CA, the SSL certificate for the CDS nodes remains unchanged, whereas it should be regenerated.

To work around this problem, remove the old SSL files (everything in /var/lib/rhui/remote_share/cds-config/ssl/) and then reinstall the CDS nodes (with rhui-manager cds reinstall --all).