Hello All,
Would like to submit the possibility of a bug in ovftool 2.1.0. Keeping things simple, we have a "fileserver" of ovfs/vmdks and our commands to ovftool started breaking after ugrading to 2.1.0 (from 2.0.1).
We dug up the command that prints out the debug info and found the (as our server logs showed), ovftool makes to GET requests to the source URL for the ovf (for whatever reason). The second of these seems is mal-formatted in 2.1.0. For comparison, I've also included similar outout from 2.0.1.
Our (neutered) deploy string: /usr/bin/ovftool --lax --machineOutput --name='vm_test1' --datastore='store1' --net:'NOWHERE'='dev' http://fileserver/file/vm.ovf vi://root:password@esxihost
Get requests (2.1.0):
2011-11-14T16:04:55.413-05:00 [7FB4D5C7B700 verbose 'Default'] CURL: => Send header GET /file/vm.ovf HTTP/1.1
--> User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
...
2011-11-14T16:04:55.420-05:00 [7FB4D5BF7700 verbose 'Default'] CURL: => Send header GET /file//vm.ovf HTTP/1.1
--> User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
Apache file server handles the extra slash ok, but our other serving option using Phusion Passenger does not, and returns a 404, which causes ovftool to return
ERROR
+ <Errors>
+ <Error>
+ <Type>ovftool.ovf.descriptor.open</Type>
+ <LocalizedMsg>
+ Failed to open OVF descriptor
+ </LocalizedMsg>
+ </Error>
+ </Errors>
RESULT
+ ERROR
Good get requests (2.0.1):
> GET /file/vm.ovf HTTP/1.1
User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
...
> GET /file/vm.ovf HTTP/1.1
User-Agent: VMware-client/4.0.0 (ovfTool; libcurl)
Can anyone else confirm or has had similar problems?