>
> Hello William,
>
Would you be able to share the playbook here?
Thanks,
Nandhakumar
--
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
@googlegroups.com
Subject: RE: [ansible-project] Re: troubleshooting ansible win problem
Thanks again Jon, yes started looking at pip to install and hopefully can
revert to 2.6 today to test if this is the problem definitively.
I use my own wsus server and its pretty beefy (just increased the pool
To: Ansible Project
Subject: [ansible-project] Re: troubleshooting ansible win problem
I tend to install ansible from pip as pip makes it easy to revert to old
versions.
I think you can install ansible via pip just for your user as well, so that's
worth exploring.
I get that it used to work
Hmm, at a glance it looks like maybe there's a problem in the error handler
where it's expecting an ErrorRecord to always be present, but in this case
it's not. If that's what's happening, it's masking whatever the real error
is because it's blowing up in the error handler. Can you file that
I tend to install ansible from pip as pip makes it easy to revert to old
versions.
I think you can install ansible via pip just for your user as well, so
that's worth exploring.
I get that it used to work, but windows updates and unknown actions taken
while you were working on other projects
Hi Jon, thanks for the input... this was all working... I believe all I did
was upgrade from ansible 2.6 to 2.8, using the same windows hosts to run
against, same user - it had been working well for 8 months or so and they
ran the updates on about 60 VMs every month. Then I was working on
I don't know what this, but I have some suggestions of things you can try.
Check the environment variables on the target host are ok. I'm wondering
if maybe it can't find a powershell module.
If this is a server 2008R2 box, make sure its had the memory fix update
applied - see
I increased memory to the VM and now getting the original error on win_ping
using domain acccount (sorry about the first post, just found the code
button)
ansible -i winhosts win-update-prod -m win_ping -vvv
ansible 2.8.0
config file = /etc/ansible/ansible.cfg
configured module search path