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/5f757f83-3507-4a4f-8ad3-7f4d2baf7be3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
