"Provider vDC" stucks as "Busy" during creation on vCD 10.

[legioon]

Hi,

I have deployed vCloud Director 10.0.1 and NSX-T 2.5.1 versions. I have configured NSX-T according to vCD requirements without any problem.

I have added vCenter and NSX-T to vCloud Director as it should be. ( I've done this many times before...). I have created network pool as GENEVE. NSX-T and vCenter appears as "Connected" on vCloud Director. That means that there is no any misconfiguration.

The problem is ;

I'm trying to create Provider VDC by select Cluster, Network pool, Storage Profile etc.. But, creation process is stucking as "Busy" for hours on end, and vCenter status is changing as "Connecting" on vCloud Director. I can cancel the creation task after the restart of vCD services via SSH. Then, vCenter status is changing as "Connected" after task cancellation.

What am i missing ?

Thanks.

[Sreec]

Can you share the logs during creation process of PVDC - vcloud-container-debug.log(/opt/vmware/vcloud-director/logs) . Also what is the version of VCSA you are running?

[oleksandrantono · Accepted solution]

I've seen this behaviour when the pVDC being created spans different vCenter datacenters. Logs showed that NSX-t manager would try to insert some duplicate records into its database and fail. IIRC I had to exclude the second DC nodes from the transport zone (either VLAN or OVERLAY or both) to workaround the problem.

[legioon]

Yes you are right. Yes you are right. NSX-T tries to add opaque network for both vcenter and gets fail. It's need to create different TZ Overlay zone for each vCenter.