If you look back through this thread, you'll see that I unistalled and then reinstalled Ansible. It didn't change anything. The core windows modules work, but not the windows modules in extras.
J On Thursday, June 11, 2015 at 11:02:59 AM UTC-5, J Hawkesworth wrote: > > I haven't tried chocolatey but I can get win_updates to execute. But my > ansible was installed via yum and I'm not on a mac. > > It does feel like something is stopping ansible from finding parts of > itself. Have you upgraded from an older ansible version (or did you start > with a fresh 1.9.1 install the first time)? Have you ever also pulled > directly from github? > > Jon > > > On Thursday, June 11, 2015 at 3:14:15 AM UTC+1, Slim Slam wrote: >> >> It originally said "path = None" but I then explicitly set the path. It >> didn't make >> a difference. Still broken. Are you able to access update and chocolatey? >> >> J >> >> On Wednesday, June 10, 2015 at 3:29:45 PM UTC-5, J Hawkesworth wrote: >>> >>> Have you set the module search path by modifying your ansible.cfg? >>> >>> My 1.9.1 install shows >>> >>> configured module search path = None >>> >>> unless I set a library= value in my ansible.cfg (maybe cos I originally >>> installed from yum though). >>> >>> >>> On Wednesday, June 10, 2015 at 5:22:45 PM UTC+1, Slim Slam wrote: >>>> >>>> Ok. I filed a documentation bug on the two windows modules which are >>>> not in Ansible 1.9.1 (but the docs don't mention that): >>>> https://github.com/ansible/ansible/issues/11220 >>>> >>>> After some further testing, it appears that the windows modules in the >>>> "core/windows" directory >>>> work ok. However, the windows modules in the "extras/windows" >>>> directory don't seem to be loading. >>>> >>>> Is my search path correct? >>>> >>>> $ ansible --version >>>> ansible 1.9.1 >>>> configured module search path = /Library/Python/2.7/site-packages/ >>>> ansible/modules/core:/Library/Python/2.7/site-packages/ansible/modules/ >>>> extras >>>> >>>> -J >>>> >>>> On Wednesday, June 10, 2015 at 8:51:05 AM UTC-5, Slim Slam wrote: >>>>> >>>>> I did "sudo pip uninstall ansible" and then "sudo pip install >>>>> ansible". Made no difference. >>>>> >>>>> yamllint.com says that my ansible script is valid. >>>>> >>>>> I'm stumped. >>>>> >>>>> J >>>>> >>>>> On Wednesday, June 10, 2015 at 7:43:33 AM UTC-5, J Hawkesworth wrote: >>>>>> >>>>>> I don't have a mac to try this out on but it seems you aren't picking >>>>>> up your modules. >>>>>> >>>>>> I did a quick search and I found a couple of threads that might be >>>>>> relevant: >>>>>> >>>>>> https://github.com/ansible/ansible/issues/5412 >>>>>> >>>>>> https://groups.google.com/forum/#!topic/ansible-project/Px4DyaHwD3I >>>>>> >>>>>> I suggest >>>>>> >>>>>> 1/ trying a clean ansible installation, if possible >>>>>> 2/ checking your playbook for invalid yaml (use a yaml-aware text >>>>>> editor like notepad++ or www.yamllint.com) >>>>>> >>>>>> Hope this helps, >>>>>> >>>>>> Jon >>>>>> >>>>>> On Wednesday, June 10, 2015 at 1:23:53 PM UTC+1, Slim Slam wrote: >>>>>>> >>>>>>> I think these might be the relevant module directories on my Mac: >>>>>>> >>>>>>> $ ls /Library/Python/2.7/site-packages/ansible/modules/core/windows >>>>>>> __init__.py win_feature.ps1 win_get_url.py win_group.pyc win_ping.ps1 >>>>>>> win_service.py win_stat.pyc >>>>>>> __init__.pyc win_feature.py win_get_url.pyc win_msi.ps1 win_ping.py >>>>>>> win_service.pyc win_user.ps1 >>>>>>> setup.ps1 win_feature.pyc win_group.ps1 win_msi.py win_ping.pyc >>>>>>> win_stat.ps1 win_user.py >>>>>>> slurp.ps1 win_get_url.ps1 win_group.py win_msi.pyc win_service.ps1 >>>>>>> win_stat.py win_user.pyc >>>>>>> >>>>>>> AND >>>>>>> >>>>>>> $ ls /Library/Python/2.7/site-packages/ansible/modules/extras/ >>>>>>> windows >>>>>>> __init__.py win_chocolatey.ps1 win_chocolatey.pyc win_updates.py >>>>>>> __init__.pyc win_chocolatey.py win_updates.ps1 win_updates.pyc >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wednesday, June 10, 2015 at 7:19:31 AM UTC-5, Slim Slam wrote: >>>>>>>> >>>>>>>> I've been installing Ansible using pip, e.g. "sudo pip install >>>>>>>> --upgrade ansible" >>>>>>>> >>>>>>>> By the way, if the only task I have is this one: >>>>>>>> >>>>>>>> tasks: >>>>>>>> - win_chocolatey: >>>>>>>> name: PSWindowsUpdate >>>>>>>> state: present >>>>>>>> >>>>>>>> I get this error: >>>>>>>> >>>>>>>> ERROR: state is not a legal parameter in an Ansible task or handler >>>>>>>> >>>>>>>> I can't get any of the Windows tasks to work, but the Linux stuff >>>>>>>> works fine. >>>>>>>> >>>>>>>> On Wednesday, June 10, 2015 at 12:54:07 AM UTC-5, J Hawkesworth >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Actually win_copy and win_file were not included in 1.9.1. They >>>>>>>>> are in 1.9.2 rc1 but there were a couple of issues with win_copy for >>>>>>>>> which >>>>>>>>> I have made fixes. I hope these will be incorporated into 1.9.2 rc2. >>>>>>>>> >>>>>>>>> Jon >>>>>>>> >>>>>>>> -- 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/55e1dc05-e95e-4a64-bcd4-0ad5bb54cdf0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
