Quantcast
Viewing all articles
Browse latest Browse all 7719

vCloud Connector 2.5 - Copy template from vSphere to vCloud Director fails

Hello all,

 

I'm trying to perform a copy of the template from the vSphere private cloud (e.g. my lab vCenter instance) to the vCloud Director private cloud (my vCD lab instance that is deployed and registered with the same vCenter instance mentioned earlier) with vCloud Connector 2.5.

 

I deployed the vCC Server component, configured, and deployed two vCC nodes - one to connect to the vCenter for vSphere private cloud config, and another one to connect to the vCloud Director org for vCD-based private cloud config. By the way, the vCloud Director is registered to the same vCenter instance that is being used for vSphere private cloud.

 

I then tried to initiate a template copy from the vSphere cloud node to the vCD node. The Export OVF Template task will begin, and the vCC plugin task will also show the copy task. The vCD instance also shows the vApp template being imported if you go to the Organization VDC properties selected during the vCC copy wizard.

 

After around 18% or so, the percentage gets stuck there for a bit before the "Export OVF Template" task fails with "Operation timed out". After that, the task shown in the vCC plugin will also eventually fail with (OVF Export failed. Null) message, and the vApp Template import task in vCD will also fail - the failed vApp will still take up the space within the assigned storage profile however until I manually delete the failed vApp Template object thru vCD.

 

Anyone else having this issue? I saw this issue on two environments so far: vCenter 5.1 Update 1 with vCD 5.1.2, and vCenter 5.5 with vCD 5.5. So the problem doesn't seem to be specific to vSphere version. The logs generated from vCC server hasn't bee all that helpful to me in figuring out what went wrong.

 

Thanks,


Viewing all articles
Browse latest Browse all 7719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>