Chapter 6. Bug fixes

Satellite follows the --foreman-foreman-url option

Before this update, if you executed the satellite-installer command with the --foreman-foreman-url option, the Foreman URL setting was not set. With this fix, the Foreman URL setting is set correctly when passed with the --foreman-foreman-url option. If you configured the Foreman URL setting before this update by using the WebUI, API, or Hammer, you must use the --foreman-foreman-url option when you run satellite-installer to preserve it. Otherwise, it is overwritten by the Foreman URL value from the answers file.

Idle Redis connections are closed after timeout

Before this update, idle Redis connections persisted because the timeout was not set for the Redis service on the Satellite Server. This led to the Pulp content workers not accepting any new connections as the open file limit was reached. Pulp content workers would fail with the Too many open files error resulting in DNF connection timeouts on the client systems. With this release, the default timeout for idle Redis connections is set to 60 seconds, after which the idle connections are closed. This prevents DNF timeouts on client systems due to Pulp reaching the open file limit.

Satellite installer no longer uses local plugins

Before this update, Puppet loaded plugins from the /opt/puppetlabs/puppet/cache/lib/ directory. As a consequence, the Satellite installer used plugins that did not match the rest of the installer modules. This update changes how the installer uses Puppet and no longer loads plugins from /opt/puppetlabs/puppet/cache/lib/. As a result, the installer only uses plugins provided by the installer, and no other plugins that could be present on the system.

Satellite preserves group membership when groupOfUniqueNames is used

Before this update, Satellite did not properly handle the groupOfUniqueNames LDAP attribute. As a consequence, user accounts from groups that were based on the groupOfUniqueNames attribute were removed from these groups upon login. This release adds support for the groupOfUniqueNames attribute. As a result, these users no longer lose group membership when logging in.

Long WebUI footer messages render correctly

Before this update, long footer messages resulted in a white block on the webUI login page. With this release, the footer message length limit is removed, which allows dynamic display. As a result, long footer messages are rendered correctly.

Alternate Content Sources with Capsule refresh content smoothly

Before this update, excessive memory consumption during Alternate Content Source (ACS) usage with Capsule led to Out of memory errors preventing ACS refresh of larger content. With this release, the ACS memory consumption issue is resolved, which allows smooth ACS refreshing of larger content.

Capsule sync does not get stuck

Before this update, wrong aiohttp session timeouts caused Capsule sync failures and incomplete downloads. With this release, the default aiohttp session timeouts are applied in Pulp when user-defined ones are not provided, preventing sync issues and enhancing user experience.

Job Template imports include all assigned organizations and locations

Before this update, some organizations and locations were missing after users imported a Job Template. With this release, when users import a Job Template, all organizations and locations that were assigned to the Job Template are imported correctly.

Lookup of images in Azure Image Gallery

Before this update, a change in the Azure Image Gallery URL format led Satellite to use a wrong URL format for image lookup. Because of this, users could not find images in the Gallery by using the gallery:// schema. Instead, they had to use the full resource URL. With this release, the Azure Image Gallery URL format is updated, and the code is changed to find images by using the new format. As a result, end users can efficiently find images in Azure Image Gallery by using the gallery:// URL schema.

Satellite removes old host keys properly when re-registering hosts

Before this update, Satellite failed to remove old host keys for re-registered hosts. As a consequence, after host re-registration, users were unable to run remote execution jobs due to host key inconsistency. With this release, host key cleanup occurs as expected in this situation. As a result, re-registered hosts no longer fail to connect during remote execution jobs due to old host keys.

Full host boot disks include mmx64.efi

Before this update, full host boot disks did not include the mmx64.efi file, leading to boot failures in specific scenarios. With this release, the boot disks include the mmx64.efi file for certain hardware boot scenarios, ensuring successful booting for users.

Consistent firmware type in compute profiles

Before this update, the Hammer command to display compute profile information failed after a Satellite upgrade. The failure occurred because the firmware type changed from EFI (Extensible Firmware Interface) to UEFI (Unified Extensible Firmware Interface), impacting VMware users. With this release, a fix ensures the consistency of the firmware type in compute profiles after Satellite upgrade. As a result, compute profile information is displayed correctly, which prevents errors in VMware environments.

Virtual TPM no longer fails in image-based provisioning on VMware

Before this update, image-based provisioning conflicted with the Virtual TPM option, causing firmware reset to BIOS and Virtual TPM disabling on hosts. As a consequence, Virtual TPM functionality failed during image-based provisioning on VMware. With this release, Virtual TPM works with image-based provisioning and firmware remains set to UEFI on the host. As a result, users can successfully enable Virtual TPM with image-based provisioning on VMware.

CloudInit default generates valid YAML output when Realm is in use

This update corrects improper indentation in the freeipa_register snippet to ensure valid YAML output. This fix ensures proper cloud-init processing, thereby resolving issues with provisioning.

Error message when discovered hosts are filtered with invalid filter fields

Before this update, when users filtered discovered hosts by using an invalid field, such as hostgroup, the browser produced infinite redirects and failed. This release fixes the infinite redirect issue in discovered hosts for invalid filter fields. As a result, discovered hosts display no hosts and log an error message with a reason.

Deprecated dict replaced with list in Cloudinit default template

Before this update, a cloud-init provisioning failure occurred due to the deprecated dict type in the Cloudinit default template. As a consequence, cloud-init provisioning failed in RHEL 9.6 due to deprecation warnings. With this release, the deprecated dict type in users configuration is replaced with the list type, and this resolves the deprecation warning. As a result, cloud-init provisioning for RHEL 9.6 and later versions is functional.

UEFI hosts redeployed automatically in PXE-boot provisioning

Before this update, redeployment of provisioned hosts could not chainload the boot loader from the hard disk correctly after subsequent PXE reboot. As a consequence, you had to modify UEFI configuration manually to redeploy the system. This release fixes the pxegrub2_chainload snippet so that the GRUB2 configuration includes paths to shimx64.efi files. As a result, you can redeploy hosts automatically.

redhat.satellite.host can update content view and lifecycle environment separately

Before this update, using the redhat.satellite.host Ansible module to update the content view or the lifecycle environment of a host resulted in an error when only one of the two parameters was changed because only changed parameters were sent to the API. With this fix, the content view and lifecycle environment are always provided together to the API. As a result, you can update the content view and lifecycle environment of the host separately.

Satellite validates the Hostname prefix Discovery setting

Before this update, the Hostname prefix (discovery_prefix) input in Satellite settings was insufficiently validated and allowed non-conforming characters. As a consequence, invalid hostnames could cause unexpected system behavior. With this release, Satellite enforces the following format for the Hostname prefix: