Ok, well I'm still mystified too, but here's a few other thoughts. Might be worth checking what is between the controller and the windows machine network wise in case there's some proxying or something. Would still be very strange behaviour for a proxy to introduce though.
I notice you have gather_facts: false might be worth setting that to true and running with -v just to see if the facts that get gathered tally with what you expect about the windows machine. Something else that might show a bit more information is if you set ANSIBLE_KEEP_REMOTE_FILES=1 before running your playbook, it won't remove the files transferred to the remote machine. From memory you'll need -vvvv to see the location where the files are transferred to. You can then at least see what powershell is being run, which might help figure out what is going on. Hope this helps, Jon On Monday, January 19, 2015 at 4:09:30 PM UTC, Dimitri Yioulos wrote: > > > Thanks, Jon. > > I have used -vvvv to get as much debugging information as possible, and I > presented it in my op. Only one instance of my playbook exists, and it > doesn't include the parameter 'IncludeManagementTools', though that was in > the example playbook that I used from Puppet documentation. It's like the > original is cached somewhere and, if it is, I don't know where that > somewhere is. As I mentioned, if I use the parameter "state: absent", the > playbook works to uninstall the service if it's installed. But it fails if > I use the parameter "state: present". Yeesh. > > Dimitri > -- 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/b93a562f-73d8-481e-97fb-3e97e557d1a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
