OVA Upload to VMware Cloud Director fails
Article ID: 380955
Updated On:
Products
Issue/Introduction
This article describes a specific failure to upload OVA catalog items or performing catalog sync to VMware Cloud Director. Comparing logs may indicate a match to this specific scenario.
OVA upload to the VMware Cloud Director instance fails
(The following are example logs, date and time will vary along with specific information)
vCloud shows successful lease acquired and posting the files to the host.
vCloud vcloud-container-debug.log:
2024-10-29 20:00:34,583 | DEBUG | vim-proxy-activity-pool-26 | ImportVAppFromOvfActivity | acquired import lease for [vcId=<vCenter ID>, moref=<VM Moref>] (timeout: 300) | requestId=xxxxxxxx-xxxx-xxxx-xxxxxxxx,request=POST https://<vCenter>/api/catalogItem/xxxxxx-xxx-xxx-xxxxxx/action/sync,requestTime=1730231965279,remoteAddress=<ip address>,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64)
.......
2024-10-29 20:00:34,604 | DEBUG | vim-proxy-activity-pool-26 | ImportVAppFromOvfActivity | uploading VfsFile[fileObject=file:///opt/vmware/vcloud-director/data/transfer/xxxxxxxx-xxxx-xxxx-xxxxxxxx/vm-<uuid>-disk-0.vmdk] to https://<ESXi FQDN>/nfc/xxxxxxxx-xxxx-xxxx-xxxxxxxx/disk-0.vmdk | requestId=13284d02-f168-4c59-9eb9-1104eb9e5bb0,request=POST https:/<VCD FQDN>/api/catalogItem/9xxxxxxxx-xxxx-xxxx-xxxxxxxx/action/sync,requestTime=1730231965279,remoteAddress=<IP Address>,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64;
ESXi vpxa log:
successful NFC session initialization:
2024-10-29T20:03:36.710Z info vpxa[2105983] [Originator@6876 sub=HttpNfcTicket opID=vcd-xxxxxxxx-xxxx-xxxx-xxxxxxxx;activity=urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx-43-01-32] [HTTP-NFC-TICKET 526af5c1-1c01-8cdf-c931-9fd73c099df0] Adding file </vmfs/volumes/<Datastore UUID>/<VM Name>/<Disk name>.vmdk>
2024-10-29T20:03:36.710Z info vpxa[2105983] [Originator@6876 sub=HttpNfcTicket opID=vcd-xxxxxxxx-xxxx-xxxx-xxxxxxxx;activity=urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx-43-01-32] [HTTP-NFC-TICKET] URL /<VM Moref>/VirtualAHCIController0:0 -> disk-0.vmdk
Host never shows these expected messages indicating the post from VCD made it to the host:
host vxpxa log example:
2024-10-24T21:39:26.835Z info vpxa[2113233] [Originator@6876 sub=HttpNfcServer opID=4d7c780c-55] HandlePost: Created DiskUploadWorker for file: /nfc/52c***************************4ea058/disk-0.vmdk
2024-10-24T21:39:26.835Z info vpxa[2113250] [Originator@6876 sub=HttpNfcServer opID=SWI-7387a5fa] [DiskUploadWorker] POST request /nfc/******************************4ea058/disk-0.vmdk
VCD times out the attempt with:
vcloud-container-debug.log
2024-10-29 20:02:34,685 | DEBUG | vim-proxy-activity-pool-26 | ImportVAppFromOvfActivity | Exception while attempting OVF import. | requestId=xxxxxxxx-xxxx-xxxx-xxxxxxxx,request=POST <VCD FQDN>/api/catalogItem/xxxxxxxx-xxxx-xxxx-xxxxxxxx/action/sync,requestTime=1730231965279,remoteAddress=<IP Address>,userAgent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...,accept=application/*+xml;version 39.0.0-alpha vcd=xxxxxxxx-xxxx-xxxx-xxxxxxxx,task=xxxxxxxx-xxxx-xxxx-xxxxxxxx activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx) activity=(com.vmware.cl.activities.LibraryItemSyncActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx) vcd=xxxxxxxx-xxxx-xxxx-xxxxxxxx,task=xxxxxxxx-xxxx-xxxx-xxxxxxxx activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx) activity=(com.vmware.vcloud.vdc.impl.CreateStoredVmActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx) activity=(com.vmware.vcloud.fabric.storage.storedVm.impl.CreateVmFromImportActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx) activity=(com.vmware.vcloud.val.internal.impl.ImportVAppFromOvfActivity,urn:uuid:xxxxxxxx-xxxx-xxxx-xxxxxxxx)
com.vmware.ssdc.util.LMException: Read timed out
Additionally, curl from the VCD cell to the host on https:// fails. (curl -k https://<esxihost>)
Environment
VMware Cloud Director 10.x
Cause
This issue can be caused by a network configuration issue; known causes are incorrect proxy settings on the VCD cells as configured in /etc/sysconfig/proxy
Resolution
Disable any proxy settings on the VMware Cloud Director cell in the environment.
Set the/etc/sysconfig/proxy file to parameter PROXY_ENABLED = "no"
Restart the VCD cell services on all cells.
Feedback
