Per another thread on this list, downgrading winrm is the temporary answer. The issue needs to be brought up with wirm upstream.
See the thread entitled "[Ansible to Windows] IndexError: tuple index out of range" https://groups.google.com/d/msg/ansible-project/XCKgXFIOras/TogpnNtuXL4J On Sat, Aug 23, 2014 at 4:10 PM, john zenou <[email protected]> wrote: > Hi all > > I have exactly the same problem and I agree too that all points to an > pywinrm issue. > Does anyone know what is causing this and how to solve it ? > > Server controle : Ansible 1.7 running on Ubuntu 12.04 > Node : Windows 2008 r2 > > -- > 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/a958126e-20f5-4e0d-a1ca-14a1a397e248%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgzuQGyoWKrC1rU9_LPLpV%2BBQhLtU%3DjzBtEDiDDy8RZFLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
