Chapter 6. Bug fixes


This section describes bugs fixed in Red Hat Satellite 6.16 that have a significant impact on users.

6.1. Web UI

Web UI displays short names of hosts consistently

Previously, some pages in the Satellite web UI displayed names of hosts as FQDNs even when Display FQDN for hosts was disabled. With this release, the Display FQDN for hosts setting is applied consistently.

Jira:SAT-21815[1]

Suggest New link for IPv4 addresses exhausted Infobox DHCP pool

Satellite suggests new IPv4 addresses in subnets with DHCP when creating or editing hosts in the UI via the Suggest New link or via the /api/subnets/:id/freeip API endpoint. Previously, when using the Infoblox DHCP provider, it would stop suggesting addresses after some time. This was because the suggestions did not expire after a period of time causing the pool of available IP addresses to be used up. With this release, the issue is now fixed.

Jira:SAT-17785

Libvirt VM details with any volume type can be accessed in the web UI

Previously, when you manually created a virtual machine with a volume type other than file in Libvirt and then attempted to access the details of the virtual machine in the web UI, Satellite produced an ambiguous error. The loading of volumes in the Libvirt compute resource has been fixed. As a result, you can access details of your virtual machines with volumes of any type in the web UI.

Jira:SAT-23211

Host details display all overridden Ansible variables

Previously, when you accessed the list of Ansible variables in Host details, Satellite displayed only the first page of Ansible variables and pagination controls were missing. The Satellite web UI has been fixed to provide pagination controls and follow the Entries per page setting. As a result, you can browse all Ansible variables that you have overridden for Ansible roles assigned to your host.

Jira:SAT-21887

Ansible jobs use passwords from Advanced fields correctly

Previously, the Ansible provider for remote execution ignored the following Advanced fields inputs from the job wizard:

  • SSH password
  • Effective user password

With this fix, the Ansible provider uses these values correctly.

Jira:SAT-18270

Ansible jobs use the SSH User field from Advanced fields

Previously, the Ansible provider for remote execution ignored the SSH User field of the Advanced fields inputs from the job wizard. The foreman_ansible component has been fixed to use the value of SSH User as the Ansible user. As a result, the Ansible provider uses this value correctly.

Jira:SAT-23947

6.2. Security and authentication

Uploading an OpenSCAP report no longer fails on hosts that run RHEL 9.4 or later with FIPS mode enabled

On Satellite hosts that run RHEL 9 in FIPS mode, uploading an OpenSCAP report previously failed with the following error:

Unable to load certs
Neither PUB key nor PRIV key

The problem has been addressed on the RHEL side and no longer affects Satellite hosts that run RHEL 9.4 or later. Note that uploading an OpenSCAP report in the described situation still fails on hosts that run RHEL 9.3 or earlier. See also Chapter 5, Known issues.

Jira:SAT-22421[1]

6.3. Content management

Checksum set value has changed

The supported --checksum-type set of sha1 and sha256 for repositories has changed to sha256, sha384 and sha512. The checksum sha1 is no longer secure and modern systems such as Red Hat Enterprise Linux 6 and up support file checksums greater than sha1. Synchronizing sha1 content is still possible but content published in repositories by Satellite will now use sha256, sha384, or sha512. The default checksum is now sha256 and not sha1.

Jira:SAT-25511[1]

6.4. Host provisioning and management

Host owner set correctly during registration

Previously, when you registered a host, Satellite set the host owner to Anonymous Admin. With this release, Satellite sets the host owner to the user who generated the registration command.

Jira:SAT-21682

Satellite uses the Default location subscribed hosts setting as the default location for registered hosts

Previously, if you did not specify the location to which you were registering the host, Satellite ignored the Default location subscribed hosts setting. With this fix, Satellite uses the value of that setting as the default location.

Jira:SAT-23047

CloudInit default no longer generates invalid YAML output

Previously, when you generated the CloudInit default provisioning template, the YAML output was incorrectly indented. The incorrect indentation caused the output to be invalid. The subscription_manager_setup snippet has been fixed to produce correct indentation. As a result, the generated YAML output is valid.

Jira:SAT-25042[1]

Path to Red Hat Image Builder image renders correctly

Previously, when you provisioned a host by using a Red Hat Image Builder image and provided a relative path to the image in the kickstart_liveimg parameter, the Kickstart default provisioning template failed to render. The Katello component has been fixed to render the absolute path of the image correctly. As a result, the Kickstart default template renders successfully and you can provision hosts by using the image.

Jira:SAT-23943

Discovery image updated with the latest RHEL 8

Previously, the Foreman Discovery image was based on Red Hat Enterprise Linux 8.6, which was limiting discovery of systems that require a later RHEL version. The Foreman Discovery image has been updated with the Red Hat Enterprise Linux 8.10.0 base. As a result, you can discover newer systems.

Jira:SAT-24197

6.5. Backup and restore

The certificate .tar file is now collected when using satellite-maintain backup on Capsule Server

Previously, the satellite-maintain backup command did not collect the certificate .tar file of the Capsule Server when creating a backup. As a consequence, restoring the archive failed. With this update, restoring the archive completes successfully in this situation.

Jira:SAT-23093

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.