vmware_guest does not connect networks

[gred7]

SUMMARY

ansible 2.9.22

vmware_guest:
hostname: "some"
username: "someone"
password: "somepass"
template: "{{ vmtemplate }}"
validate_certs: false
folder: ""
datacenter: qarea
name: "{{ tempname }}"
state: poweredon
guest_id: ubuntu64Guest
cluster: "DRS"
disk:
- size_gb: "{{ disksize }}"
type: thin
datastore: DSS
hardware:
memory_mb: "{{ memsize }}"
num_cpus: "{{ ncpus }}"
scsi: paravirtual
networks:
- name: Localnet
start_connected: yes
type: dhcp
when: "{{ localnet | bool == true }}"
- name: AS
start_connected: yes
when: "{{ asnet | bool == true }}"
wait_for_ip_address: true
delegate_to: localhost
register: deploy_vm

ISSUE TYPE

• Bug Report

COMPONENT NAME

vmware_guest

ANSIBLE VERSION

ansible 2.9.22
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.12 (default, Mar  1 2021, 11:38:31) [GCC 5.4.0 20160609]

CONFIGURATION

empy

OS / ENVIRONMENT

ubuntu linux
Linux jenkins 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

STEPS TO REPRODUCE

 vmware_guest:
      hostname: "some"
      username: "someone"
      password: "somepass"
      template: "{{ vmtemplate }}"
      validate_certs: false
      folder: ""
      datacenter: qarea
      name: "{{ tempname }}"
      state: poweredon
      guest_id: ubuntu64Guest
      cluster: "DRS"
      disk:
        - size_gb: "{{ disksize }}"
          type: thin
          datastore: DSS
      hardware:
        memory_mb: "{{ memsize }}"
        num_cpus: "{{ ncpus }}"
        scsi: paravirtual
      networks:
        - name: Localnet
          start_connected: yes
          type: dhcp
          when: "{{ localnet | bool == true }}"
        - name: AS
          start_connected: yes
          when: "{{ asnet | bool == true }}"
      wait_for_ip_address: true
    delegate_to: localhost
    register: deploy_vm

EXPECTED RESULTS

when set to true both(or one of) networks are connected on VM poweron

ACTUAL RESULTS

networks are added but left unconnected. in vm i see 2 interfaces with NO CARRIER/DOWN state.
if I log into vsphere web interface I see both networks in unconnected state.
by hands. I am able to set them to connected, then VM interfaces are up, and got ip addresses.

[ansibullbot]

Files identified in the description:

• [plugins/modules/vmware_guest.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/vmware_guest.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @Akasurde @Tomorrow9 @goneri @lparkes @nerzhul @pdellaert @pgbidkar @warthog9
click here for bot help

[gred7]

also I do not see the case of two networks (or rather more than one) in your tests

[alex1989hu]

I can verify the behaviour what @gred7 reported: networks are added but left unconnected. Additionally, Connect At Power On option is also not checked. In my case, I faced that issue after upgrading Ansible from 2.9.13 to 4.1.0 - and there was only one network card.

[phreakocious]

This happens when vmware tools does not report that guest OS customization completed successfully. Unfortunately, it seems to even happen when customization is not requested. Also fairly confident that I started seeing this behavior after a recent upgrade.

[Udayendu]

I can verify the behaviour what @gred7 reported: networks are added but left unconnected. Additionally, Connect At Power On option is also not checked. In my case, I faced that issue after upgrading Ansible from 2.9.13 to 4.1.0 - and there was only one network card.

I am using ansible 4.1.0 and not facing this atall. Deploying more than 100+ OVA and templates in my vCenter. If the customization wont work then it wont attach the interface.

$ pip3 show ansible
Name: ansible
Version: 4.1.0
Summary: Radically simple IT automation
Home-page: https://ansible.com/
Author: Ansible, Inc.
Author-email: info@ansible.com
License: GPLv3+
Location: /usr/local/lib/python3.8/dist-packages
Requires: ansible-core
Required-by:

• For windows, here is what I am using:

- name: Deploying vm from '{{ win_temp }}'
  vmware_guest:
    hostname: '{{ vcenter_hostname }}'
    username: '{{ vcenter_username }}'
    password: '{{ vcenter_password }}'
    datacenter: '{{ vsphere_datacenter }}'
    cluster: '{{ vsphere_cluster }}'
    datastore: '{{ vsphere_datastore }}'
    name: '{{ inventory_hostname }}'
    template: '{{ win_temp }}'
    folder: '{{ folder }}'
    validate_certs: 'no'
    networks:
    - name: '{{ Mgmt_network }}'
      ip: "{{ Mgmt_network_ipv4 }}"
      netmask: '{{ Mgmt_network_nmv4 }}'
      gateway: '{{ Mgmt_network_gwv4 }}'
      dns_servers:
        - '{{ dns_server1 }}'
        - '{{ dns_server2 }}'
    state: poweredon
    wait_for_ip_address: yes
    customization:
      hostname: "{{ vsphere_vm_hostname }}"
      dns_suffix: '{{ ad_domain }}'
      domainadmin: '{{ ad_domain_admin }}'
      domainadminpassword: '{{ ad_domain_password }}'
      joindomain: '{{ ad_domain }}'
      timezone: '{{ timezone }}'
    wait_for_customization: yes
  delegate_to: localhost

• For linux, here is what I am using:

- name: Deploying vm from '{{ lin_temp }}'
  vmware_guest:
    hostname: '{{ vcenter_hostname }}'
    username: '{{ vcenter_username }}'
    password: '{{ vcenter_password }}'
    datacenter: '{{ vsphere_datacenter }}'
    cluster: '{{ vsphere_cluster }}'
    datastore: '{{ vsphere_datastore }}'
    name: '{{ inventory_hostname }}'
    template: '{{ lin_temp }}'
    folder: '{{ folder }}'
    validate_certs: 'no'
    networks:
    - name: '{{ Mgmt_network }}'
      ip: "{{ Mgmt_network_ipv4 }}"
      netmask: '{{ Mgmt_network_nmv4 }}'
      gateway: '{{ Mgmt_network_gwv4 }}'
      device_type: vmxnet3
      connected: True
      start_connected: True
      type: static
    state: poweredoff
    customization:
      hostname: "{{ vsphere_vm_hostname }}"
      domain: '{{ dns_domain }}'
      dns_servers:
        - '{{ dns_server1 }}'
        - '{{ dns_server2 }}'
  delegate_to: localhost

Hope this may help you.

[GreyArea765]

Also seeing the same issue on vSphere 6.7 deploying Linux machines, let me know if any debug output is required.

Ansible version

$ ansible --version
ansible 2.10.11
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/mattb/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0]

Workstation OS

$ lsb_release -a
LSB Version:	core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal

[GreyArea765]

As an aside, I worked around this issue by adding an arbitrary wait timeout and then applying the connected states again, thought it might be useful for anyone finding this issue like I did.

- name: Wait 30 seconds for VM deployment
  wait_for:
    timeout: 30

- name: Fix unconnected network 
  vmware_guest:
    hostname: '{{ vc_ipaddress }}'
    username: '{{ vault_vc_username }}'
    password: '{{ vault_vc_password }}'
    validate_certs: False
    datacenter: '{{ vc_datacenter }}'
    name: '{{ vm_name }}'
    networks:
      - name: '{{ vc_vm_net_name }}'
        connected: yes
        start_connected: yes

[Udayendu]

As an aside, I worked around this issue by adding an arbitrary wait timeout and then applying the connected states again, thought it might be useful for anyone finding this issue like I did.

- name: Wait 30 seconds for VM deployment
  wait_for:
    timeout: 30

- name: Fix unconnected network 
  vmware_guest:
    hostname: '{{ vc_ipaddress }}'
    username: '{{ vault_vc_username }}'
    password: '{{ vault_vc_password }}'
    validate_certs: False
    datacenter: '{{ vc_datacenter }}'
    name: '{{ vm_name }}'
    networks:
      - name: '{{ vc_vm_net_name }}'
        connected: yes
        start_connected: yes

wait_for is usually not needed if you will use "connected: yes" in the main play as I have mentioned earlier.

[GreyArea765]

@Udayendu not for me, I have connected and start_connected both set to yes in the initial Play and still the interface doesn't get connected. Perhaps that's a difference between your 4.1.0 and my 2.10.11?

        connected: yes
        start_connected: yes