# vmware\_guest module and template cloning vs vm update weirdness on NIC addition **URL:** \ **Category:** Ansible Project\ **Tags:** rhel\ **Created:** [November 11, 2017, 11:56am UTC](https://forum.ansible.com/t/vmware-guest-module-and-template-cloning-vs-vm-update-weirdness-on-nic-addition/25998 "2017-11-11T11:56:14Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Bruno](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Bruno](https://forum.ansible.com/u/Bruno)\ **Post date:** [November 11, 2017, 11:56am UTC](https://forum.ansible.com/t/vmware-guest-module-and-template-cloning-vs-vm-update-weirdness-on-nic-addition/25998/1 "2017-11-11T11:56:14Z")
Hi all, Ansible version used : 2.4.1.0 I am experiencing some strange behaviour using vmware\_guest to create a new VM from a template, compared to updating a previously createdVM : I am trying to create a VM from a template (connecting to vCenter 6.0u2, the template being a RHEL 7.3); this template has only one network interface, and I want to add a new NIC in my playbook (by specifying its type, IP, …) When I create the VM from the template (setting 2 NICs in playbook), all is OK : the VM is OK, the new interface is created and I have both network configuration scripts created and working (/etc/sysconfig/network-script/ifcfg-en\*) However, on a freshly created VM which only has one network interface, when updating it with vmware\_guest module to add another NIC, the interface is correctly added to the VM, but the interface is not configured on the guest side (ifcfg-en224 script is not created, no IP configured). It also seems that changing a NIC IP does not get propagated to the ifcfg- script, and the IP is not updated on guest. Do you have any clue on where the issue could come from ? It seems to work perfectly on disks (adding, resizing a disk is ok), but not on network interfaces. Regards, Bruno