vmware_guest_network: Add network adapter to vm about community.vmware HOT 5 CLOSED

@StratosSamouilidis
in network section
name - it's portgroup name on vCenter, not {{ name_of_adapter }}
This playbook work fine:

    - name: Add network
      community.vmware.vmware_guest_network:
        hostname: "{{ vc_server }}"
        username: "{{ domainadminUser }}"
        password: "{{ domainadminPassword }}"
        cluster: "{{ vc_cluster }}"
        datacenter: "{{ vc_datacenter }}"
        validate_certs: no
        name: test_vm
        gather_network_info: false
        networks:
          - dvswitch_name: "{{ vc_vm_dwsName }}"
            name: "{{ vc_vm_portGroupName }}"
            device_type: vmxnet3
            connected: true
            start_connected: true
            state: new

from community.vmware.

@StratosSamouilidis: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

• component name

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE/bug_report.md

click here for bot help

from community.vmware.

I am having the identical issue:

If I run this play:

- name: add a nic 
  community.vmware.vmware_guest_network:
    hostname: '{{ inventory_hostname }}'
    username: "{{ user }}"
    password: "{{ pass }}"
    datacenter: "{{ datacenter }}"
    validate_certs: no
    connected: yes
    name: AlpineTest
    switch: ACI
    network_name: Webinar|StretchApp1|EPG1
    state: present`

The result is that I end up with a new port-group created nowhere really

As you can see in the picture the is now a PG Webinar|StretchApp1|EPG1 at the datacenter level not connected to any switch. It will be delete when I delete the VM or the NIC.

I would want the VM to be placed in the ACI dVS port group called Webinar|StretchApp1|EPG1
I am running: ansible 2.9.13 and the latest community.vmware ansible galaxy v1.2.0

from community.vmware.

resolved_by_pr #401

from community.vmware.

@StratosSamouilidis @camrossi Could you please verify if PR #401 fixes the issue for you? Thanks,

from community.vmware.