Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-17 Thread Chris Church
"local_action" and "delegate_to: localhost" should both be working again with Windows hosts. There may still be another issue delegating to another host, which is being tracked by https://github.com/ansible/ansible/issues/12370. On Sat, Sep 12, 2015 at 6:18 PM, Frank Perks wrote: > delegate_to:

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-12 Thread Frank Perks
delegate_to: localhost seems to work okay for most cases when working in a playbook. Unfortunately the solution doesn't seem to work when doing it inside a role: - wait_for host={{ ansible_ssh_host }} port={{ ansible_ssh_port }} delay=30 timeout=300 delegate_to: localhost I get: "ERROR! The

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-10 Thread J Hawkesworth
Looks like you have hit https://github.com/ansible/ansible/issues/12053 changing over to delegate_to: localhost will likely work around the problem for now, until the above can be fixed. Jon On Thursday, September 10, 2015 at 9:09:20 AM UTC+1, Trond Hindenes wrote: > > That is very strange.

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-10 Thread Trond Hindenes
That is very strange. I spent a lot of time making sure it would work in both 1.9 and 2.0. Will test and report back. On Wednesday, September 9, 2015 at 5:46:39 PM UTC+2, Frank Perks wrote: > > Just to add something else, in 1.9.4 both Trond and my stuff works fine. > > On Wednesday, September 9

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Frank Perks
Just to add something else, in 1.9.4 both Trond and my stuff works fine. On Wednesday, September 9, 2015 at 10:44:35 AM UTC-4, Frank Perks wrote: > > Hi Trond, > > I tried your module, and it fails with the same issue as above. > > fatal: [52.8.31.205]: FAILED! => {"failed": true, "msg": "ERROR!

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Frank Perks
Hi Trond, I tried your module, and it fails with the same issue as above. fatal: [52.8.31.205]: FAILED! => {"failed": true, "msg": "ERROR! The module stat was not found in configured module paths"} I have found a really ugly way to get around it, and that is by simply defining another play wi

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Trond Hindenes
Frank, I actually put a lot of work into the trondhindenes.win_reboot role you can find on Galaxy. WIth it you can force reboots, run reboots for nodes needing a reboot or whatever, and it will correctly run cooldown scripts and loop until it has a stable winrm service running before it will al

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Frank Perks
This is running latest version of devel (i updated this morning). delegate_to / connnection: local does not seem to work. On Wednesday, September 9, 2015 at 8:45:47 AM UTC-4, Brian Coca wrote: > > What version of ansible? have you tried with connection: local or > delegate_to: localhost:? > >

Re: [ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Brian Coca
What version of ansible? have you tried with connection: local or delegate_to: localhost:? It seems we lookup the module before making the connection local, in which case it is still looking for .ps1 files. -- Brian Coca -- You received this message because you are subscribed to the Google G

[ansible-project] Can't use local_action in Windows playbook in devel?

2015-09-09 Thread Frank Perks
I am trying to reboot a windows server after installing .net + a bunch of dependencies. I have a super simple PS module to schedule a reboot. However afterwords i would like to wait for the WinRM connection to come back: - name: Configuring windows hosts: windows roles: - win_dotnet_46