Tested with several Ansible versions (2.7.x, 2.8.x) - always with same result: VM is created, but gets wrong IP caused by wrong MACs (all NICs).ĭebugged the Python code behind and might found a bug in This was cloning the template into a running VM.unfortunately with same MACs as the template. So we then have 3 templates with the same MAC and a VM running with the same MAC. We use a process in which a base template is cloned 2 times in a GitLAB CI pipeline and enhanced each step with more applications. This is then automatically resolved by vCenter by changing it's MAC address but still not the behaviour you want. First of all this is not what the vCenter console does and second of all if the template is then converted to a VM we get a MAC conflict triggered alert. The VM is cloned with the same MAC address as the template.
This is what actually happens when you use the vCenter console. The VM is cloned from the template with a different MAC address than the template.
Version: 14 # Hardware version, latest will be supported in Ansible 2.10 name: Clone new VM from template and customize
