VMware Aria Automation services fail to deploy with vco-app pod in a restart loop due to CEIP telemetry timeout

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In VMware Aria Automation, services may fail to deploy correctly following a system restart. You may observe that the deploy.sh script fails to complete, and several Kubernetes services remains in a Pending state. Specifically, the Orchestrator (vco-app) pod enters a continuous restart loop because it cannot pass its startup probes.

Environment

* Product: VMware Aria Automation 

• Component: Orchestrator / vco-app

Cause

This issue occurs when the Customer Experience Improvement Program (CEIP) is enabled. During startup, the Orchestrator server attempts to transmit data to a legacy telemetry server. If that server is unresponsive or times out, the telemetry library blocks the initialization of the REST API and other critical Spring services, causing the Kubernetes startupProbe to fail.

Resolution

We have scheduled a fix for this issue in the forthcoming Aria Automation 8.18.1 Patch 5.

Workaround:

Disable telemetry (CEIP) to bypass the blocking connection and redeploy the services:

1. Log in to the Aria Automation appliance via SSH.

2. Disable CEIP by running the following command: vracli ceip off

3. Restart the deployment process to bring the services online: /opt/scripts/deploy.sh

Additional Information

It is recommended to Subscribe to this knowledge article to receive updates regarding a permanent fix for this telemetry handling behaviour.