hello,
I believe that issue https://github.com/ansible/ansible/issues/13763 still isn’t resolved as I am experiencing it currently.
I am using version 2.0.0.2
Here is an example script that will cause the same error message as in the issue above
`
Based on that issue, and the corresponding commit that resolved the problem, the fix does not exist in 2.0.0.2. It was first introduced for the 2.1 release.
https://github.com/ansible/ansible/commit/c4cbeeffa89a6265483c187f493bc90ef13bbac9
You would need to upgrade to at least v2.1.0.0-1
Is there any chance that the comment can be updated then to reflect that it didn’t actually make it into 2.0? If I had known it was actually in 2.1 I would have upgraded sooner