After reading what seemed like a bazillions support thread on Vmware, I
managed to make the sequence work with this workaround:
1- Make sure the NIC in the template is "disabled"
2- In the playbook, in your vmware_guest task, under networks, make sure to
add start_connected: yes
networks:
start_connected: yes
The sequence should work fine after that. The slight delay to reactivate
the NIC seems enough to make sure the guestOs won't start trying to join
the domain at the same time there are changes made to the networking parts
of the guest.
On Thursday, 2 August 2018 08:34:26 UTC-4, Sylvain Martel wrote:
>
> To anyone else that might encounter this problem, I found this thread:
> https://groups.google.com/forum/#!searchin/ansible-project/vm$20stuck|sort:date/ansible-project/H_0FhXkm2ns/-TvY5Fc1AgAJ
>
> which mention this article :
> http://www.hurryupandwait.io/blog/getting-readytroubleshooting-unattended-windows-installation
>
> <http://www.google.com/url?q=http%3A%2F%2Fwww.hurryupandwait.io%2Fblog%2Fgetting-readytroubleshooting-unattended-windows-installation&sa=D&sntz=1&usg=AFQjCNEP8upQV2-qKEPup9pq6NWTPVaSqQ>
>
> It helped me to debug the problem and it's not related to ansible.
>
> My best guest is that the MAC conflict happens at the worst of time and
> prevent the correct domain discovery. Maybe if there was a way to include
> a small delay in task to ensure the MAC address change happens before, but
> that would be though.
>
> Thanks.
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/12a4a85b-3ab4-4915-b80f-85e2329f9df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
