Dell Automation Platform Components

The Dell Automation Platform orchestrator displays a critical alert for the modification to the security setup of Orchestrator Microsegmentation. Alert code 0x20010002 is shown.

The deployment fails when Network Time Protocol (NTP) is set using Fully Qualified Domain Name (FQDN) for OVA installation of the Dell Automation Platform 1.x.

When upgrading a Dell Automation Platform (DAP) from version 1.2 to 2.0 using the production bundle or OVA, the upgrade may fail or experience significant delays. The issue is caused by a large accumulation of NATS Jetstream streams created by the drift service over time. During upgrade, the system processes all streams, leading to long execution time, resource exhaustion, or failures. Additional upgrade failures may occur due to NATS configuration parsing issues.

Dell Automation Platform remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

This article describes issues seen during an attempted default TLS certificate with a custom certificate via Portal UI.

When configuring a network proxy with an FQDN that contains special characters fails browser-side validation, preventing the proxy from being saved.

Customers may encounter warning alerts about EDGE_HZP_DEVICE_CAT0 license exhaustion in Dell Automation Platform environments with PowerStore storage. This is a benign issue caused by storage onboarding incorrectly attempting to consume licenses.

This article is designed to aid a user to determine the container sizing requirements for Orchestrator External Connection vCenter.

Java-based containerized applications (such as Keycloak) may experience unexpected termination due to out-of-memory (OOM) errors when running on Linux Kernel 6.12 or later. This issue stems from changes in how the kernel exposes "cgroup" memory limits. These changes affect the Java Virtual Machine's (JVM) ability to detect and respect container memory constraints correctly.

In DAP‑2.0.0.0 and later release, attempting to download the Inductive Automation (Ignition) Blueprint from the Portal Catalog to the Orchestrator may result in a conflict error. This occurs when the blueprint has already been downloaded directly from the Orchestrator UI instead of the Portal, and the Portal Catalog is not notified of that action. As a result, the Portal believes that the blueprint already exists and blocks the download. The issue is limited to this blueprint, and a workaround is available.

In DAP‑2.0.0.0 SaaS environments, dynamic licensing may fail when Dell Automation Platform Orchestrator (DAPO) is provisioned through the UI using an SaaS entitlement. Although the Orchestrator deployment completes successfully, the dynamic license is not applied, and users are prompted to upload a file‑based license. This issue is specific to SaaS portal entitlement synchronization and does not impact on-premises deployments. A workaround is available while a fix is planned for a future SaaS patch.

In DAP‑2.0.0.0, when a storage asset is removed from the Orchestrator and then re‑added through the Portal Add Assets dialog, the Portal UI may display a misleading error message stating "asset already exists." Despite the error, the storage asset is re‑assigned to the Orchestrator successfully in the backend. This issue is caused by stale Portal UI state and does not impact the functional usability of the re‑added storage asset.

In DAP‑2.0.0.0 SaaS, users whose organization has only on‑premises entitlements may see the License card disabled in the Dell Automation Platform SaaS Portal. As a result, these users are unable to add a License Authorization Code (LAC), which blocks self‑service provisioning of an SaaS Orchestrator through the UI.

In DAP‑2.0.0.0 SaaS environments, bulk onboarding of Non‑FDO devices through the Portal Assets page may result in onboarding errors when one or more devices in the bulk request have an unreachable IP address. Although individual onboarding of the same devices succeeds, including an unreachable device in a bulk request can cause all devices using the same proxy to fail onboarding.

In DAP‑2.0.0.0, the License Authorization Code (LAC) is displayed inconsistently between SaaS and on-premises environments during orchestrator provisioning or licensing workflows. In SaaS, the LAC is masked (only the last few characters are shown), while in on-premises licensing flows the full LAC is visible in the license selection drop‑down. This behavior is intentional for certain self‑service workflow.

After upgrading to DAP‑2.0.0.0, cluster node metrics may fail to display when VLAN bond networks are configured and used for VM deployment or migration. Metrics such as network traffic are missing for nodes using VLAN bond interfaces, while nodes without VLAN bond configuration continue to show metrics correctly.

A NativeEdge Asset reports an incorrect IP address for its management address.

Dell Automation Platform 1.2, Virtual Machines (VMs) fail to obtain an IP address using DHCP when connected to a bridge Virtual Network Segment (VNS) backed by a heterogeneous bond interface (a bond consisting of Ethernet and Wi-Fi). This behavior is the result of a deliberate architectural design choice to ensure broad compatibility with wireless networks.

In Dell Automation Platform 1.2.0.0, resuming a failed Dell Private Cloud Node Add deployment without deselecting uninstall workflow option can trigger the license plug-in Uninstall workflow to de‑register the entire cluster license, causing subsequent license expansion to fail. The issue occurs because the license plug-in followed the default blueprint life cycle and performed the de‑registration step during uninstall.

This article explains an issue where the kernel drivers fail to detect one of the NVIDIA Graphics Processing Units (GPU) in a Unified Extensible Firmware Interface (UEFI) Virtual Machine (VM) configured with multiple GPU passthroughs.

In Dell Automation Platform 1.2.0.0, Windows‑based blueprint deployments may fail during post‑deployment automation when Ansible attempts to run WinRM-based tasks on the Windows virtual machine (VM). The VM deploys successfully, but blueprint automation fails with errors indicating that the WinRM command input was too large. This is caused by Ansible-core 2.19, where the generated PowerShell payload is larger than in Ansible-core 2.18, exceeding the command-size limits supported by Windows WinRM. This issue affects only Windows blueprints that use WinRM; Linux-based blueprints and Windows VMs that do not rely on WinRM-based automation are not impacted.

This article describes a deployment scenario that has been observed to cause memory oversubscription on a NativeEdge Virtual Machine (VM). Memory oversubscription may result in loss of access to the affected VMs.

Dell Private Cloud – Red Hat remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

Dell Private Cloud - VMware remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

This article explains common configurations with a NativeEdge Endpoint that prevent the configuration of a network bond.

This article describes a condition with a NativeEdge Endpoint incorrectly reporting its IP address. The situation may be observed after the Endpoint's provisioning, or after a reboot.

This article describes an issue that may occur during the boot process of a NativeEdge Virtual Machine (VM) running Windows after it was shut down. Sometimes, the VM may stop responding during POST due to a specific Windows configuration setting.

This article describes an endpoint state that occurs when a USB Factory Reset Image is inserted into the wrong endpoint. This halt state is triggered during the endpoint’s reboot or power‑on sequence following a shutdown.

After Dell Private Cloud PowerEdge node restore on Dell Automation Platform 1.2.0.0 and earlier, hardware inventory may show missing components (network cards, BOSS, storage controllers). This is due to a defect in the "hzp‑inventory" service that prevents Redfish data from refreshing. A permanent fix is planned for the next release. For versions 1.2.0.0 and earlier, restart the "hzp‑inventory" pod as a workaround.

Users are observing the inconsistency of the download behavior of the Dell support site when download.OVA file.