VCF Automation Upgrade Prechecks pre-check result status: Failed for ClusterComputeResource:domain-#####
search cancel

VCF Automation Upgrade Prechecks pre-check result status: Failed for ClusterComputeResource:domain-#####

book

Article ID: 452544

calendar_today

Updated On:

Products

VCF Automation

Issue/Introduction

VCF Automation Upgrade Prechecks precheck result status: Failed

The precheck under Tasks fails with the following error output:

Platform Health Check Error [platform-vmsp-platform-validate-resources-vsphere-resources : unable to validate vSphere objects: unable to resolve <ObjectType> identifier <ObjectType>:<ID> ServerFaultCode: The object 'vim.<ObjectType>:<ID>' has already been deleted or has not been completely created] [VCFMS-HEALTH-002]

Environment

Aria Automation 8.18.1

VCF Automation 9.1

Cause

The compute cluster referenced by the vmsp control plane was deleted and recreated (e.g., during an ESXi host upgrade), resulting in a newly assigned Managed Object Reference ID. The vmsp control plane pd configuration continues to point to the stale compute cluster value, which causes the vSphere object validation to fail during the upgrade precheck phase.

Resolution

This issue is resolved by identifying the new infrastructure name or path in vCenter and updating the Provider Definition (pd) configuration within the VCF Automation vmsp-platform namespace to match it.

For complete step-by-step instructions on how to verify and update this configuration, please see the hub article: How to modify the Provider Definition (pd) configuration in VCF Automation.

Additional Information

Do not modify datastore values if they are not correct. This procedure is covered in Storage configuration mismatch between VCF management components and vCenter causes VCF to fail upgrade or patching.