Loading...
Loading...
Dell Automation Platform Orchestrator installation fails with a message similar to the example below: 2025/08/28 13:03:14 clean loaded images success Getting image loader logs EO Image Loader completed Deleting EO image loader EO Images loader uninstalled Uninstalling PORTAL if already exists... Deleting k8s resources... Portal uninstalled Orchestrator chart exists. Skip unarchive... Portal chart exists. Skip unarchive... Portal Installation has started OperationType: INSTALL OperationStatus: IN_PROGRESS ChartKey: PORTAL OperationType: INSTALL OperationStatus: COMPLETED ChartKey: PORTAL secret/dapp-root-ca created OperationType: POST_INSTALL OperationStatus: IN_PROGRESS Getting delco service logs Deleting delco-svc deployment OperationType: POST_INSTALL OperationStatus: COMPLETED dap-portal has deployed successfully Getting organization ID... Organization ID: f47ac10b-58cc-4372-a567-0e02b2c3d479 Getting access token... Access token: eyJh***************Ahe Creating configmap. configmap/delco-config created Orchestrator chart exists. Skip unarchive... Portal chart exists. Skip unarchive... Orchestrator Installation has started OperationType: INSTALL OperationStatus: IN_PROGRESS ChartKey: ORCHESTRATOR OperationType: INSTALL OperationStatus: FAILED ChartKey: ORCHESTRATOR native-edge-orchestrator has NOT deployed and has status: failed Refer to the logs (/home/user/logs/neo-install-helm-output-2025.08.28-12.49.08.log) for more details. Saving logs to files Cleaning up the execution log file The user sees that the installation failed due to the 1-hour installation timer when reviewing the relevant log file (in this case, the neo-install-helm-output-2025.08.28-12.49.08.log ). The user sees the log spending a lot of the time trying to get the deployment hzp-security-svc to complete when reviewing the log. ready.go:277: [debug] Deployment is not ready: dell-automation/hzp-security-svc. 0 out of 1 expected pods are ready ready.go:277: [debug] Deployment is not ready: dell-automation/hzp-security-svc. 0 out of 1 expected pods are ready ready.go:277: [debug] Deployment is not ready: dell-automation/hzp-security-svc. 0 out of 1 expected pods are ready If the user looks at the deployment log for hzp-security-svc , they see the following message repeatedly. {"level":"error","error":"performing request: Get \"https://portal.local.edge/api/v1/oidc/.well-known/openid-configuration\": tls: failed to verify certificate: x509: certificate is valid for default.dell.com, *, rv.local.edge, rv.dell.fdo, rv.internal.use.only, rv1.local.edge, rv1.dell.fdo, rv2.local.edge, rv2.dell.fdo, rv3.local.edge, rv3.dell.fdo, rv4.local.edge, rv4.dell.fdo, rv5.local.edge, rv5.dell.fdo, rv6.local.edge, rv6.dell.fdo, rv7.local.edge, rv7.dell.fdo, rv8.local.edge, rv8.dell.fdo, rv9.local.edge, rv9.dell.fdo, rv10.local.edge, rv10.dell.fdo, rv11.local.edge, rv11.dell.fdo, rv12.local.edge, rv12.dell.fdo, rv13.local.edge, rv13.dell.fdo, rv14.local.edge, rv14.dell.fdo, rv15.local.edge, rv15.dell.fdo, rv16.local.edge, rv16.dell.fdo, rv17.local.edge, rv17.dell.fdo, rv18.local.edge, rv18.dell.fdo, rv19.local.edge, rv19.dell.fdo, rv20.local.edge, rv20.dell.fdo, not portal.local.edge","time":"2025-09-11T19:39:32Z","message":"Error fetching OIDC config."} This error message means that the certificate retrieved from the portal does not match what is expected and causes the installation to fail.
The reason for the failure is that in DAP an ingress was created for the orchestrator during installation of *.local.edge . This caused the lookups for the hzp-security-svc to the portal to fail as they were going to the wrong direction due to the ingress.
Do not use local.edge as a cookie domain. If this is not an option for the user, engage NativeEdge Escalation Engineering for further assistance.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.