Known issues

When the payload location and the repository location are configured on different servers, remediation jobs on Oracle Enterprise Linux 8 can fail.

When a VMware vCenter Server is imported by using an AMO proxy–based connection, the vCenter Server object may be visible only to the BLAdmins role and not to other roles.

When PXE and DHCP are configured on the same server and a target system is booted in UEFI mode, the PXE server may fail to generate the boot answer file in the tftproot directory. As a result, the network boot process does not proceed as expected.

When a patching job that was originally created with analysis‑only is later updated to enable remediation, executing an earlier run of the same job against the same targets may still trigger remediation. In this case, the job details continue to indicate analysis‑only, even though remediation is performed.

When a large volume of data is involved, opening jobs or displaying job results may take longer than expected. In such cases, batch job runs that are marked for soft delete may not be selected correctly, and child job runs are not marked as soft‑deleted. As a result, these job runs are not cleaned up as expected.

When an Infrastructure Blackout Window is enabled while a patch analysis job with remediation is in progress, the remediation step may fail because job execution is blocked. However, the parent patch job continues to display a success status (green tick), even though remediation did not run successfully.

23.4.00

When a VMware vCenter Server is imported into TrueSight Server Automation by using an AMO proxy–based connection, users may not be able to expand or browse the VMware vCenter Server object. In this scenario, the object is readable only by users with the built‑in BLAdmins role, while other internal roles are unable to view or access it.

When provisioning Windows targets using EFI or Secure UEFI boot, the PXE boot process may fail because the required boot configuration file is not created under the pxelinux.cfg directory.

When performing a stand-alone PXE installation or configuration on a Red Hat Enterprise Linux 10 server, the PXE configuration may fail with a database write error. In this scenario, the PXE service fails to start, causing the PXE installation or configuration to fail.

When snapshot jobs track configuration files, change tracking may report differences due to variations in value ordering, even if no real changes were made.

When using pagination with the compliance job run results REST API, the total_records value can represent only the current page count instead of the total available records.

When a user authenticates by using a non‑SRP authentication type and runs the BLCLI command to change a password, the user is able to change the BLAdmin password successfully. This occurs even though the user is not logged in by using SRP authentication.

When the RSCD agent is installed successfully on SUSE Linux Enterprise Server 12 SP5 running on the ppc64le architecture, the agent may fail to start after installation.

When using the Remove Ovaldi Directory option during agent installation with native AIX or Solaris installers, the Ovaldi directory is not removed as expected. The installation completes, but the Ovaldi directory remains present on the target system.

When accessing the Server Information widget, it can fail to display server details and be hidden from the user interface. This occurs because the underlying query used to retrieve host information is not supported on Microsoft SQL Server 2016, resulting in errors while fetching server data.

A scheduled batch job configured to run on the first Saturday of every month at a specific time may be skipped and not executed as expected. In such cases, the job does not run for the affected month, and the next execution is scheduled for the following month.

The offline downloader may fail for SUSE Linux Enterprise Server 15 SP6 and SP7. During execution, the download process does not complete successfully and reports validation or connectivity errors, causing metadata generation for the repository to fail.

Windows provisioning using EFI or Secure UEFI may fail because the required PXE boot configuration file is not created under the pxelinux.cfg directory.

Standalone PXE installation or configuration on Red Hat Enterprise Linux 10 may fail with a database write error. In this scenario, the blpxe service fails to start, preventing PXE installation or configuration from completing.