On 15.02.2017 10:28, Adrian Paraschiv wrote:
Because I said it's a role and you put them as tasks ;)
Sorry about that, I didn't think it would matter, but it does.
Testet the tasks in a role and it stopped as you say.
Testet Ansible 2.1.4.0 and 2.2.0.0 and there it works as expected, so
this bug/behaviour was introduced in 2.2.1.0.
--
Kai Stian Olstad
--
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/a7e1d8f717b287e584bd47dd56b7e666%40olstad.com.
For more options, visit https://groups.google.com/d/optout.
