VMware Aria Automation 8.x upgrade to VCFA 9.0.2 fails at Stage 6 with error LCMVSPHERECONFIG1000095 due to crashing vco pods

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When performing an upgrade of VMware Aria Automation from version 8.18.1 to version VCFA 9.0.2 using VCF Operations, the upgrade sequence fails explicitly during Stage 6 (New Cluster / Nodes Deployment).
• The deployment UI halts and returns the following signature error code: LCMVSPHERECONFIG1000095
• Prior to or during this failure, engineering analysis reveals that the underlying VMware Aria Automation Orchestrator (vco) pods are entering an unstable, crashing cycle.
• This state blocks the bootstrap validation routine of the new services platform engine (installvmsp), resulting in a hard failure of the upgrade workflow.

Environment

 

• Source Infrastructure: VMware Aria Automation 8.18.1 (Minimum supported baseline)

• Target Infrastructure: VCF Automation 9.0.2

• Lifecycle Engine: VCF Operations 9.0.x Fleet Management Appliance

Cause

• The failure occurs because the underlying VMware Aria Automation Orchestrator (vco) pods crash during the phase where data validation hooks are executed.
• This loop is driven by an incompatible or corrupted vCenter Server plug-in tracking configuration within the legacy database structure before migration.
• Because Stage 6 attempts to deploy the new container infrastructure and validate hooks on the target vCenter, any systemic dependency failure in the source pods triggers the LCMVSPHERECONFIG1000095 failure rule.

Resolution

To remediate this failure, you must repair the legacy Orchestrator pod state on the source environment, clean up the failed deployment state, and then proceed with the newly structured VCF Automation 9.0.x upgrade sequence.

Phase 1: Remediate the Source vco Pods

1. Log in to your source VMware Aria Automation 8.18.1 infrastructure deployment.

2. Upgrade or re-apply the vCenter Server plug-in (vc plugin) strictly to version 8.2.2.

3. Track and verify via CLI that all vco pods stabilize into a persistent Running state and cease crashing.

4. Execute an Inventory Synchronization for VMware Aria Automation directly within VMware Aria Suite Lifecycle before proceeding.

Phase 2: Clear Failed State and Prepare VCF Operations

1. Log in to the VCF Operations 9.0.x Fleet Management Appliance.

2. If the failed upgrade state remains locked, delete the Automation component reference from VCF Operations, re-import it cleanly from the legacy Aria Suite Lifecycle, and ensure its hostname maps explicitly to an FQDN (fleetmgmt.yourdomain.com).

3. Ensure the VCF Operations Fleet Management Appliance hostname is a valid FQDN using the following commands via SSH:

   hostname -f
   

   (Note: If a shortname is returned, it must be remediated to an FQDN before starting).

4. Configure your Depot and download the upgrade payload via VCF Operations → Fleet Management → Lifecycle → VCF Management → Binary Management → Upgrade Binary.

5. Map out your new target execution matrix by navigating to Components → Plan Upgrade, selecting target version 9.0.2, and clicking Create Plan.

Phase 3: Execute the Upgrade Sequence & Monitor Lifecycle Stages

Select Upgrade next to VCF Automation and supply your network infrastructure matrix (Primary VIP, Cluster CIDR, Node Prefix, and the Cluster Node IP Pool containing 2 new IPs for Simple or 4 new IPs for Clustered deployments).