VMware: vmware_guest throws vmdk already exists

[nicolaibaralmueller]

SUMMARY

vmware_guest throws error that vmdk already exists although it does not. It is created during running the module but somehow fails.

pyvmomi-6.7.1.2018.12

ISSUE TYPE

• Bug Report

COMPONENT NAME

vmware_guest

ANSIBLE VERSION

2.8.1

STEPS TO REPRODUCE

- name: Create new VM
  vmware_guest:
    hostname: "{{ vcenter_hostname }}"
    esxi_hostname: "{{ esxi_host }}"
    username: '{{domain_user}}'
    password: "{{ domain_user_password }}"
    validate_certs: False
    datacenter: TM
    name: "{{ vm_hostname }}"
    folder: "{{ vm_destination }}"      
    state: poweredon
    disk:
    - size_gb: '{{ disk_size }}'
      type: thin
      autoselect_datastore: True
    hardware:
      memory_mb: "{{ memory }}"
      num_cpus: "{{ cores }}"
      num_cpu_cores_per_socket: "{{ cores }}"
    networks:
    - name: LAN
      domain: "{{ domain }}"
      dns_servers:
      -  "{{ dns1 }}"
      -  "{{ dns2 }}"
      type: static
      ip: "{{ ip }}"
      netmask: 255.255.254.0
      gateway: 192.168.1.5
    customization:
      autologon: True
      hostname: "{{ vm_hostname }}"
      domain: "{{ domain }}"
      password: vagrant
      domainadmin: "{{ domain_user }}"
      domainadminpassword: "{{ domain_user_password }}"
      joindomain: "{{ domain }}"
      timezone: 105
      runonce:
      - powershell.exe -ExecutionPolicy Unrestricted -File C:\StartupScripts\ConfigureRemotingForAnsible.ps1 -ForceNewSSLCert -EnableCredSSP
      - powershell.exe -ExecutionPolicy Unrestricted -File C:\StartupScripts\DisableFirewall.ps1 
    wait_for_customization: yes
    template: "{{ vm_template }}"
    wait_for_ip_address: yes

EXPECTED RESULTS

Should just create the VM.

ACTUAL RESULTS

Failed to create a virtual machine : Cannot complete the operation because the file or folder [EL02] ********/********.vmdk already exists"

[ansibot]

Files identified in the description:

• lib/ansible/modules/cloud/vmware/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

[ansibot]

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

[ansibot]

@nicolaibaralmueller, just so you are aware we have a dedicated Working Group for vmware.
You can find other people interested in this in #ansible-vmware on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

[Akasurde]

@nicolaibaralmueller Thanks for reporting this issue. Could you please check if PR #58737 works for you and let me know ? Thanks

needs_info

[Akasurde]

resolved_by_pr #58737

[cgoeller]

Will this bug be fixed in Ansible 2.8.3 ?

[Akasurde]

@cgoeller I have created backport PR #59087 and once this is merged, change will be available in 2.8.3.
Thanks.