Yes, but without so much verbose. turns out to be a known bug in pywinrm, fixed in current tree. installing from github fixed it.
if you have the same problem, wait till pywinrm-0.3.1 (or whatever version) is out, or git clone https://github.com/diyan/pywinrm cd pywinrm pip install --upgrade . then just pip upgrade as usual when the fix is released. On Saturday, May 5, 2018 at 2:42:56 AM UTC-7, Tom Rota wrote: > > Have you tried letting vagrant bring the box up without running the > ansible portion of provisioning, getting your command prompt back, and then > running ansible-playbook site.yml -vvvvv ? > > > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/5a08d05e-0314-428a-ba8e-65daadeca931%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
