After upgrading to ovftool v4.4, ovftool started breaking on a specific ExtraConfig parameter. It seems to be working correctly with all other ExtraConfigs, but adding a specific entry is causing it to break.
With a standard set of ExtraConfig parameters specified in envoy-proxy-bae.ovf. Conversion to OVA goes through perfectly.
<vmw:ExtraConfig ovf:required="true" vmw:key="guest.command.enabled" vmw:value="false"/>
```
ubuntu@cdm-node:~$ ovftool --allowAllExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Opening OVA target: test.ova
Writing OVA package: test.ova
Transfer Completed
Warning:
- Wrong file size specified in OVF descriptor for 'envoy-proxy-base-1.vmdk' (specified: -1, actual 910012416).
Completed successfully
```
However, when we add the following entry to the list of ExtraConfigs, ovftool fails.
<vmw:ExtraConfig ovf:required="true" vmw:key="sched.mem.pin" vmw:value="true"/>
```
ubuntu@cdm-node:~$ ovftool --allowExtraConfig envoy-proxy-base.ovf test.ova
Opening OVF source: envoy-proxy-base.ovf
The manifest validates
Error: OVF Package is not supported by target:
- Line -1: Unsupported value 'sched.mem.pin' for attribute 'key' on element 'ExtraConfig'.
Completed with errors
```
Why is this specific ExtraConfig breaking ovftool? Is there something different about the naming that is causing the issue? Why do we only see this issue when this specific ExtraConfig is added to the ovf?