VCF Automation and vCenter relation appears to be broken post-upgrade to 9.1

Products

• VCF Automation

Issue/Introduction

• VCF Automation is recalling stale configuration artifacts from version 9.0.2.

• The integration relationship between VCF Automation and vCenter Server is impacted or entirely disconnected.

• An inability to locate options to clean up the 9.0.2 artifacts or redeploy the VCF Automation component from the UI.

Environment

• VCF Automation 9.1

• vCenter Server

Cause

This issue can occur if the initial deployment of version 9.0.x had a partially attempted onboarding of content. If underlying resources, such as workload domains, were deleted as part of a manual cleanup effort prior to the upgrade, old stale data is left behind in the VCF Automation component database. This stale data persists through the 9.1 upgrade and breaks the vCenter connection once VCF Automation is at version 9.1.

Resolution

WARNING: Proceed with these steps ONLY if your environment matches the exact symptoms and cause described above, and there is no production data in the VCF Automation environment that needs to be retained. Redeploying the component is a destructive action that permanently removes existing VCF Automation data.

If there is no production data inside this environment that needs to be retained, completely remove the stale data by redeploying the VCF Automation component.

1. Follow the steps located in KB 441333.

2. Recreate all necessary underlying resources, such as the deleted workload domains.

3. Redeploy a fresh instance of the VCF Automation component.