I'm running ansible 1.9.4 (released in Oct 2015) and am hitting a bug
that has been fixed in August 2015, but the fix is apparently in ansible
2.0 only.
Manually applying the fix to my 1.9.4 installation resolves the problem.
I'm running ansible 1.9.4 (released in Oct 2015) and am hitting a bug
that has been fixed in August 2015, but the fix is apparently in ansible
2.0 only.
Manually applying the fix to my 1.9.4 installation resolves the problem.