In VCF Automation, navigating to Infrastructure > Supervisors displays the message: No Supervisors created.
The vCenter Server connection status appears healthy within VCF Automation, and vCenter inventory synchronizes successfully.
In the vSphere Client, the Supervisor cluster is present and its status is displayed as Running.
Users are unable to proceed with creating Regions or continuing the VCF Automation configuration.
Reconnecting the vCenter in VCF Automation or recreating the Supervisor Cluster in vCenter does not resolve the issue.
VCF Auto / VCFA: 9.x, 9.1
VCF: 9.0, 9.1
[email protected] account.Remove the manually added endpoint and allow VCF Automation to configure it with the correct service account automatically.
Log in to VCF Automation as an administrator.
Navigate to Administration > Connections > vCenter.
Locate and delete the manually configured vCenter endpoint that is using the [email protected] account.
Log into VCF Operations with the local admin user.
Navigate to VCF Operations > Operate > Administration > Integrations, locate the VCF Automation instance, and refresh.
Go back to VCF Automation and navigate to Administration > VCF Instances
Click on the kebab menu (⋮) button next to the VCF instance we want to import and select Refresh.
A new vCenter endpoint will be automatically populated using the appropriate service account.
Navigate back to Infrastructure > Supervisors and confirmt the Supervisor details are now populating successfully.
If the vCenter is imported as Disabled with a NO Connected state due to a certificate error, run through the following