VCF Operations Management Activation Fails for Imported vCenter Due to Adapter Mismatch
search cancel

VCF Operations Management Activation Fails for Imported vCenter Due to Adapter Mismatch

book

Article ID: 438541

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • After performing a brownfield import of a workload domain vCenter in VMware Cloud Foundation, the following issues occur:
    • The vCenter object does not appear in the VCF Operations Licensing section.
    • Attempts to activate management for the vCenter within the Integrations UI fails. The system returns the error: "The selected VCF cloud accounts are not eligible for activating management." 

    • An "Internal Server Error" is displayed while validating the vCenter connection in the Integrations UI.

    • The inventory shows the workload domain object, but the vCenter object is absent.

Environment

  • VMware Cloud Foundation 9.0.x
  • VCF Operations 9.0.x

Cause

The VMware Cloud Foundation adapter instance for the imported vCenter was created manually within VCF Operations instead of allowing the automated SDDC Manager synchronization process to deploy it. In VCF 9.0 architecture, SDDC Manager must natively push the configuration and bind workload domain vCenter adapters. Manual creation causes an object UUID mismatch and orphaned objects that lack the required internal mappings for management activation and licensing visibility

Resolution

  1. Generate snapshots of all VCF Operations cluster nodes.
  2. Log in to the VCF Operations UI as an administrator.
  3. Navigate to Integrations.
  4. Delete the manually created VMware Cloud Foundation adapter instance(s) associated with the affected workload domain vCenter.
  5. Wait for the next automated collector cycle to execute. This allows SDDC Manager to natively redeploy the adapter and establish correct UUID bindings.
  6. Verify the system redeploys the adapter automatically and the vCenter object appears in the inventory without UUID conflicts.
  7. Navigate to the Licensing section and assign the appropriate license to the newly discovered vCenter object