I’ll happily do the grunt work of creating the issue in git once I confirm this. Is there something else wrong with these properties?
So I would expect these to be in the OVF file right? I have found that these are successfully passed into the VM as it is created providing you use the -allowExtraConfig switch on the ovftool. The guest info properties are very similar to those that existed on CL and are the means to pass in the ignition file data. So whatever automated process Fedora is using to generate this ova is not working properly. Once I do all this, I can get a valid vmx file that I can use with my packer build.Ĭompare this to the 1688.5.3.ova for the pre-fedora CoreOS and that ova works just fine. So if you really needed those to be set on the vmx file, you have to edit the resultant vmx file yourself to add them. However, ovftool messes this up and does not propagate those properties to the resultant vmx file. In order for ovftool to build, these need to be specified using the -prop switch.
So what is the deal with with the Property error? The ovf has two properties which are marked as required:
Import ovf vmware professional#
I am having this same issue with VMWare Fusion Professional Version 11.5.1 (15018442) using 31.20200127.3.0.ova for Fedora CoreOS.