We found ovftool fails to deploy a vApp instance, within which 12VMs are to be created, from an ova file, while it succeeds if the ova file contains a slimmer version ovf file (VMs' no is decreased to 8). The host where ovftool runs is in the same LAN with VCenter server so network is probably not a problem. Besides, it also succeeds to deploy the package.ova file using VSphere Client GUI.
ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin
--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation
The progress bar indicating complete percentage never shows up for the 12VM-version's deployment. The verbose log shows that the upload never starts. Has anybody encountered this issue? And you'll be appreciated if you can give us a hand. And we are willing to provide our ova file to troubleshooting this issue.
Background
We generate an OVA file which contains multiple VMs. Every VM specified in the ovf file refers to either a Linux vmdk or a Win vmdk within the OVA file. With two vmdk files contained in the ova file, the file size is almost 3G. We used the above command to deploy an vApp instance, but it always fail.
The following are what we have tried.
- The machine to run ovftool always keeps in the same LAN as VCenter server. This ensures network low latency.
- We tried ovftool both with its linux's version and windows's version. Deploying the ova containing 12VMs, always fail; deploying the slimmer version with 8VMs, it works;
- The difference between 12VM and 8VM ovafiles are very simple: both has two vmdk files, file-size are almost the same(~3G). It's just the latter ovf file choose to generate small number of homogenous VMs.
The verbose logs are attached below.
ovftool --X:logToConsole --noSSLVerify --name=DBaaS-fail --vmFolder=BuildValidation --powerOffTarget --overwrite '--net:VMNetwork=VLAN138' --datastore=store1800-1 --diskMode=thin
--prop:BaseIP=ww.xx.yy.zz --prop:Netmask=255.255.255.128 --prop:Gateway=ww.xx.yy.253 '--prop:DNS_Servers=10.132.71.1 10.132.71.2' --acceptAllEulas --powerOn /mnt/DATA/release/XXXXX/ova-demo/package.ova vi://user:password@10.ab.cc.dd/vCHS-DBaaS/host/ALMA/Resources/BuildValidation
ŠŠŠŠŠŠŠŠ.
-->
Opening VI target:
vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation
2014-01-17T08:15:55.791Z [7FCDED7D2740 verbose 'Default'] Hostsystem used
as deploy target: vim.HostSystem:host-16
Deploying to VI:
vi://root@10.146.25.129:443/vCHS-DBaaS/host/ALMA/Resources/BuildValidation
2014-01-17T08:16:24.172Z [7FCDED7D2740 verbose 'Default'] Using file size
as progress measure
2014-01-17T08:16:24.189Z [7FCDE4FB0700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.190Z [7FCDE416F700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.190Z [7FCDE412E700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.190Z [7FCDE40ED700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.191Z [7FCDE40AC700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.192Z [7FCDE406B700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.192Z [7FCDBFFFF700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.195Z [7FCDE4FB0700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.197Z [7FCDE416F700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.197Z [7FCDE412E700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.197Z [7FCDE40ED700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.198Z [7FCDE40AC700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.199Z [7FCDE406B700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:24.199Z [7FCDBFFFF700 verbose 'Default'] CURL: header
data removed
2014-01-17T08:16:42.512Z [7FCDBFF7D700 verbose
'HttpConnectionPool-000001'] [RemoveConnection] Connection removed; cnx:
<SSL(<io_obj p:0x00007fcde0014b00, h:-1, <TCP '0.0.0.0:0'>, <TCP
'10.146.25.129:443'>>)>; pooled: 0
work@boxbuilder:~$ lsof -i TCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ovftool.b 31731 work 7u IPv4 574157 0t0 TCP
10.146.25.131:33750->10.146.25.129:https (ESTABLISHED)
ovftool.b 31731 work 9u IPv4 575678 0t0 TCP
10.146.25.131:33752->10.146.25.129:https (ESTABLISHED)
ovftool.b 31731 work 10u IPv4 574954 0t0 TCP
10.146.25.131:57555->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 11u IPv4 574159 0t0 TCP
10.146.25.131:57556->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 12u IPv4 576636 0t0 TCP
10.146.25.131:57557->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 13u IPv4 574955 0t0 TCP
10.146.25.131:57558->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 14u IPv4 574160 0t0 TCP
10.146.25.131:57559->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 15u IPv4 576637 0t0 TCP
10.146.25.131:57560->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)
ovftool.b 31731 work 16u IPv4 574956 0t0 TCP
10.146.25.131:57561->w2-tempest-ucs001-30.eng.vmware.com:https (CLOSE_WAIT)