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/7cfe961e-ff10-4809-90b1-bd2108336f9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
