Day 2 Power Operations Fail in Fleet Manager After Out-of-Band vCenter Migration

Products

• VCF Automation

Issue/Introduction

During a VMware Cloud Foundation (VCF) upgrade, administrators may experience a critical failure where Day 2 lifecycle operations—specifically "Power OFF" and "Power ON"—fail when triggered from the Fleet Manager (Aria Suite Lifecycle). As a result of this failure, the VCF Automation (VCFA) environment becomes stranded in a scaled-down, offline status.

An evaluation of the application programming interface (API) reveals a critical discrepancy in the backend /environment/ JSON body:

• The "Product Details" payload correctly references the new, active vCenter endpoint.

• The "Infrastructure Resources" metadata still points to an old, obsolete vCenter endpoint.

Environment

 

VCF Automation 9.0.2

VCF Fleet Manager 9.0.2

 

Cause

The original Aria Automation environment was imported into Fleet Manager while it still resided on a legacy vCenter. Subsequently, a manual "lift and shift" was performed—the virtual machines were re-IP'd and vMotioned to a new vCenter. Because this move was executed outside of Fleet Manager's awareness, the underlying infrastructure metadata was never updated to reflect the new location.

Resolution

Force Fleet Manager to run a fresh data collection against the cluster, explicitly overwriting the stale /environment/ JSON body and synchronizing the metadata to the new vCenter endpoint.

Action Plan:

1. Navigate to Fleet Manager: Log into the Aria Suite Lifecycle (Fleet Manager) user interface.

2. Execute Import: Initiate a new Import Environment operation for the affected VCFA deployment.

3. Target New Endpoint: Ensure the import configuration explicitly targets the new, active vCenter endpoint where the VMs currently reside.

4. Validate: Once the import completes successfully, validate the fix by executing a test Day 2 "Power OFF" and subsequent "Power ON" action.