Unable to import Velocloud OVA files directly to Content Library.

Products

• VMware vCenter Server

Issue/Introduction

• Importing a VeloCloud OVA directly to the content library results in below error:

A general system error occurred: The import of library item ########### has failed.
Reason: Error transferring file velocloud-orchestrator-test.vmdk to ds:///vmfs/volumes/vsan:###########//contentlib-##########/#############/velocloud-orchestrator-test_#########.vmdk?serverld=###############
Error during transfer of ds///vmfs/volumes/vsan:################//contentlib-############/###########/velocloud-orchestrator-test_##########.vmdk?serverid=###############: Pipe closed.

• ISOs and templates can be imported to content library without any issues on vSphere client.
  
  
• OVA upload through ESXi host client works fine.
  
  
• Import task hangs and fails at 1%
  
  
• On the ESXi host, var/run/log/hostd.log

yyyy-mm-ddTHH:MM:SS warning hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC ERROR]NfcNetTcpSetError: Unexpected EOF
yyyy-mm-ddTHH:MM:SS warning hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC ERROR]NfcNetTcpRead: EOF should not be reached
yyyy-mm-ddTHH:MM:SS warning hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC ERROR]NfcNet_Recv: requested 264, recevied only 0 bytes
yyyy-mm-ddTHH:MM:SS warning hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC ERROR]NfcGetMessage: NfcNet_Recv failed: NFC_NETWORK_ERROR
yyyy-mm-ddTHH:MM:SS warning hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC ERROR]NfcServerProcessClientMsg: Failed to get message from client: NFC_NETWORK_ERROR (The operation experienced a network error)
yyyy-mm-ddTHH:MM:SS error hostd[2104871] [Originator@6876 sub=Nfcsvc opID=#####] Read error from the nfcLib: NFC_NETWORK_ERROR (done = yep)
yyyy-mm-ddTHH:MM:SS info hostd[2104871] [Originator@6876 sub=Libs opID=#####] [NFC INFO]NfcServer_SessionCleanup: Cleaning up server session with currentState: NFC_STREAM_RECEIVING
yyyy-mm-ddTHH:MM:SS info hostd[2104871] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=#####] Event 15942 : NFC operation 'Upload' for path '[vsanDatastore] contentlib-#############/################/velocloud-orchestrator-test_##########.vmdk' was initiated from '192.168.#.#' and completed with status 'Failure'.

• On the VCenter, var/log/vmware/content-library/cls.log

yyyy-mm-ddTHH:MM:SS | DEBUG    | m7n4145w-9453-auto-7am-h5:70001833-76 | cls-simple-activity-18    | DownloadSessionServiceImpl     | failing download session #########-####### with error message Error transferring file velocloud-orchestrator-test.vmdk from http:/. Reason: IO error during transfer of http:/: java.io.IOException: Broken pipe

Environment

VCenter Server 7.x

Cause

The manifest file of the VeloCloud OVA seems to get corrupted during the import process into the Content Library.

 

Resolution

• Login to vSphere UI and navigate to the appropriate vCenter Server where you want to deploy the VeloCloud OVA.
  
  
• Right-click on the desired folder or resource in the inventory and select "Deploy OVF Template".
  
  
• Select the desired VeloCloud OVA image and deploy with the desired on-screen settings.
  
  
• Once deployed, right click on the VM and select clone as Template to content-library. Click the drop down against Template type and select OVF.
  
  
• The VeloCloud OVA is now saved as OVF on the content library.

Additional Information

• Direct import of VeloCloud OVAs to content library has not been tested by VeloCloud Engineering.
  
  
• OVF can be again converted back to OVA format using OVFTool

command-

cd into the directory where ovf file and related vmdk exists and perform below operation

ovftool <file-name>.ovf <desired-file-name>.ova

 

For more information on ovftool utility commands, please refer this link - Command-Line Options

To Download ovftool, please refer this link - Open Virtualization Format (OVF) Tool