Error: Unable to connect to vCenter/sdk failed when adding vCenter to VCF Operations

Products

• VCF Operations

Issue/Introduction

Issue/Introduction When attempting to add a standalone vCenter to VCF Operations, the configuration fails to save, and the following errors are displayed in the UI:

Unable to connect to VC: Connecting to VC at https://<vcenter>/sdk failed. Please check connectivity.
VC extensions info check task failed

Environment

VCF Operations 9.1

Cause

When using the default collector group, the vCenter Server must be reachable from all nodes within the VCF Operations cluster, including replica and Data nodes. This issue occurs when a firewall blocks connectivity between the any node and the vCenter Server.

Resolution

To verify if all nodes can reach the vCenter Server, connect to each node via SSH and run the following command:

curl -vk https://<vcenter_fqdn>

To resolve the issue:

Ensure that the network firewall allows outbound connectivity from all VCF Operations nodes to the vCenter Server.

Workaround:

If the firewall cannot be immediately adjusted, consider bypassing the connectivity check on the culprit node by explicitly assigning the adapter instance to any other node where connectivity is present.

Note: It is not recommended to pin the adapter to a specific node. If the node the adapter is pinned to goes down, the adapter is not able to move to another node and must be moved manually. This is a temporary workaround.