"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 <[email protected]> wrote:

> 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 module wait_for was not found in configured module
> paths" Is there any other sort of workaround that exists (i cannot live
> without blocks anymore).
>
> On Thursday, September 10, 2015 at 5:35:49 AM UTC-4, J Hawkesworth wrote:
>>
>> 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. 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, 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! 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 with the wait_for winrm. Then starting another play
>>>>> for the remaining windows tasks.
>>>>>
>>>>>
>>>>> On Wednesday, September 9, 2015 at 10:29:05 AM UTC-4, Trond Hindenes
>>>>> wrote:
>>>>>>
>>>>>> 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
>>>>>> allow continuation. Maybe see if that solves this exact case for you?
>>>>>>
>>>>>> as for connection: local, I've had far better results with
>>>>>> delegate_to: localhost on the current devel branch.
>>>>>>
>>>>>> On Wednesday, September 9, 2015 at 3:38:03 PM UTC+2, Frank Perks
>>>>>> wrote:
>>>>>>>
>>>>>>> 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:?
>>>>>>>>
>>>>>>>>  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 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/1f2359f7-1c80-4419-94b9-8e8dd656101f%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/1f2359f7-1c80-4419-94b9-8e8dd656101f%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> 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/CAH%2BKTJ7jbX3ffh5PKoNGCj0shdNuvFpM25ROQf1VFa%3Dj0FmJog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to