I have been given an externally generated OVF that the ovftool verifies as perfectly fine and shows me that there are End-user license agreements. However, when I use vCenter (4 and 5) to Deploy OVF Template, the EULA page does not show any text when displaying the license and asking me to Accept. After various comparisons with other OVFs and manipulation of the original OVF, I have determined that the vCenter deploy is having trouble when the OVF contains the ovf: prefix on certain XML elements.
For example, the OVF that does not work has the ovf: prefix on all elements (<ovf:Envelope>, <ovf:References>, <ovf:File>, <ovf:Strings>) and also has the ovf: prefix on the Internationalization file (ovf:Strings, ovf:Msg). This does not show errors in the ovftool, but the license text does not display during vCenter OVF deploy.
If I hand edit the OVF and remove the ovf: prefix on the elements listed above, the ovftool shows no errors and the license text now shows up during vCenter OVF deploy!
Is this a bug in vCenter Deploy OVF Template?
Thanks.