Were did you get this OVA template? Was it exported from a VM to a OVA?? If yes are you sure that did not had an ISO attached in the Virtual CDROM when was exported??
I'm seeing the same exact error Failed to deploy VM: postNFCData failed when attempting to deploy the GitHub Enterprise 2.6.4 appliance on ESXi 6.0 U2.. google shows nothing except this forum. How disappointing.
Wondering what exactly postNFCData is trying to do when it is failing? Obviously NFC (Network File Copy) is not completing, but why ???
Also I would like to add that all disks on this system are INTERNAL SAS & SATA so the disk file copy should not be traversing the network, but the local datastores.
This is really looking more and more like a bug, I have had the same exact problem on two different ESXi 6U2 implementations, in two separate environments.
I had this same issue and just for kicks I chose Thin Provisioning instead of Thick and I was able to install an appliance. This was one of the only threads on this error so I thought I would share my experience.
We fixed an issue in the recently released host client version 1.9.1 that could cause a large OVA to fail to deploy. The VIB is available here: http://labs.vmware.com/flings/esxi-embedded-host-client
Would any of you be able to try that and confirm if the issue is resolved?
I'd also be interested to know which browser/OS you're using.
I apologise for the long delay in finding this.
I was trying to deploy an OVA as well from a Ubuntu 16.04 workstation. The browser I was using was Chrome and it would fail out.
The fix for me was to use Firefox instead of Chrome. !
Tried on CentOS 6.8 in both Firefox and Chrome, still fails. Tried using version v1.10.1.
Used OVFTool instead.
I tried this .vib and it did not seem to work for me. Used current Firefox on OSX Sierra.
Switching to Firefox helped to resolve such issue. Still experiencing the issue while using Chrome browser.
I think I have some insight into this failure now. For VMs that have been exported with ovftool using the --compress argument, the Host Client is unable to deploy them because the ESXi host expects the uncompressed disk images to be uploaded, and we have, unfortunately, no good way to un-gzip those disk images using the web browser at the moment.
For now, you will have to use ovftool to import VMs with compressed disk images.
Just hit this when trying to deploy an F5 VE appliance into my lab.
This is the syntax I used with OVFtool, maybe useful for anyone else in this situation.
ovftool -dm=thin -ds=Datastore1 -n=BIGIP-188.8.131.52.0.249.ALL-scsi --net:External="VM Network" --net:HA="Isolated Network" --net:Internal="VM Network" --net:Management="Isolated Network" "BIGIP-184.108.40.206.0.249.ALL-scsi.ova" vi://email@example.com
Thanks for the command DataBitz. That worked perfectly for me.
had the same issue whilst deploying BigIp VE on ESXi 6.5. Thank you for the solution DataBitz!
I am facing same issue and found that there is one Linux file attached to the VM I exported from VM Workstation the file is Linux and 60 MB while as the machine I exported is 256 GB. How can I deal with this do i need to detach the Linux file from the machine and start new export?