Trying to use Ansible to configure Windows Server 2008 and am having some basic problem.
The server is running on Amazon AWS. I’ve got all the connection stuff working fine.
This (mostly empty) Ansible playbook runs fine:
How did you install ansible, if it is a checkout did you --recursive to add the submodules ? seems like ansible is not able to see the modules in the modules path.
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.
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)
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.
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?
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?
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.