Open Akasurde opened 4 years ago
Files identified in the description:
If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
cc @Tomorrow9 @goneri @lparkes @pgbidkar @warthog9 click here for bot help
@ba31 Are you still facing this issue? Thanks.
needs_info
Hi Team, Do we have any fix/work around for the above issue. i m able to recreate it now.
"msg": "Failure validating OVF import spec: Line 76: Unable to parse 'enableMPTSupport' for attribute 'key' on element 'Config'."
FYR, Below is my ansible version.
ansible [core 2.11.1] config file = /etc/ansible/ansible.cfg configured module search path = ['/home/blr/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/local/lib/python3.8/dist-packages/ansible ansible collection location = /home/blr/.ansible/collections:/usr/share/ansible/collections executable location = /usr/local/bin/ansible python version = 3.8.6 (default, Oct 6 2020, 04:02:53) [GCC 5.4.0 20160609] jinja version = 2.11.2 libyaml = False
Any inputs are highly appreciated.
Thanks Shiva
@Akasurde This issue is waiting for your response. Please respond or the issue will be closed.
So, the enableMPTSupport
thing could be a red herring as far as the red result is concerned.
Indeed, I am getting the same warning out of a working (yellow status) community.vmware.vmware_deploy_ovf
upon register:
ing it, then dumping its status with a subsequent debug
task.
Ansible core 2.13.11, Mac OS X 13.4.1 (c) (22F770820d), Intel i7, community.vmware
2.8.0
enableMPTSupport quite exists.. any workarounds to get around?
enableMPTSupport
option is part of OVA/OVF spec and part of spec VM from VirtualVideoCard section, and warning can be ignored. VM must me deployed with last version of module.
From @ba31 on May 01, 2020 18:12
When I disable the "fail_on_spec_warnings" it does not fail although do not deploy any VM
ISSUE TYPE Bug Report
COMPONENT NAME vmware_deploy_ovf
ANSIBLE VERSION
OS / ENVIRONMENT vSphere 6.7.0.30000
STEPS TO REPRODUCE
ACTUAL RESULTS
Copied from original issue: ansible/ansible#69281