Can't convert cluster to vLCM Single Image Managed

Products

• VMware vCenter Server

Issue/Introduction

• Clusters under VC 80u3 (Build 24091160)  cannot be converted from baselines to vLCM Single Image.

 

• The task may fail with the error "Error occurred while checking whether NSX-T Data Center is enabled on this cluster" / " Feature cannot be enabled on this cluster"

 

• NSX 4.2.0.1 is enabled on this cluster
• NSX Service Account is enabled for the vCenter.

vum-server.log

[YYYY-MM-DDTHH:MM:SS] info vmware-vum-server[12045] [Originator@6876 sub=EHP] Refreshing JWT
[YYYY-MM-DDTHH:MM:SS] info vmware-vum-server[11982] [Originator@6876 sub=EHP] JWT refresh successful
[YYYY-MM-DDTHH:MM:SS] info vmware-vum-server[11554] [Originator@6876 sub=JsonUtils] [JsonUtils 67] JsonApiGet called. apiPath: /api/v1/transport-node-collections?vc_instance_uuid=########-####-###-####-############&cluster_moid=domain-c####&check_vlcm_eligibility=true
[YYYY-MM-DDTHH:MM:SS] warning vmware-vum-server[598702] [Originator@6876 sub=HttpConnectionPool-000000] Failed to get pooled connection; <cs p:00007ff0a85689a0, TCP:nsx_fqdn:443>, (null), duration: 11msec, N7Vmacore24InvalidArgumentExceptionE(Certificate too long (max 2103) for SSL connection: '-----BEGIN CERTIFICATE-----

 

 

Environment

VMware vCenter 8.0 Update 3 

Cause

This error is caused by a known issue when the vLCM is unable to get the information about the the cluster from the NSX-T managers to validate if the cluster is configured with NSX due to an SSL connection issue.  

Resolution

This issue is fixed in 8U3b or later versions. 

Update the vCenter to a version that contain fix and attempt to convert the cluster. 

Additional Information

VMware vCenter Server 8.0 Update 3b Release Notes