Open tezzigator opened 4 years ago
Hi @tezzigator
Thank you for reporting this issue.
I think that this issue occurs cause is the wrong specified value to the networks param.
The networks param specify portgroup name that not a network device name.
networks: "{u'configured ovf portgroup name':u'dvp name to attache'}"
Is the eth0 in your ovf configuration it portgroup name?
<rasd:Connection>eth0</rasd:Connection>
In that case, for example, the networks param is the following.
networks: "{u'eth0':u'CUST-302'}"
cc @Akasurde @Tomorrow9 @goneri @lparkes @pgbidkar @warthog9 click here for bot help
@tezzigator This issue is waiting for your response. Please respond or the issue will be closed.
SUMMARY
For a playbook, instead of connecting the VMs nic to my VMWare VDS-based DPG that is named CUST-302, my VM's nic gets connected to a different (non-VDS) VMWare network that is called SHARED
ISSUE TYPE
COMPONENT NAME
vmware_deploy_ovf
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
$ uname -a Linux wat-utl-jmp 3.10.0-1127.el7.x86_64 #1 SMP Tue Feb 18 16:39:12 EST 2020 x86_64 x86_64 x86_64 GNU/Linux $
STEPS TO REPRODUCE
generic deploy playbook
EXPECTED RESULTS
VM created with its NIC attached to the VMWare VDS-based DPG called CUST-302.
ACTUAL RESULTS
The VM gets created but it's NIC gets assigned to a completely different (non-VDS) VM network that is called SHARED.
OTHER INFO
I do not use "VMNetwork"m or "Network 1" or "Adapter 1" as my OVA has this embedded info: