J Hawkesworth <j.r.hawkesworth <at> googlemail.com> writes: > > > HeyIf you are using ansible from a source (git checkout) then just do what the message says and rungit submodule update --init --recursiveThis will then pick up the modules (which are stored in git submodules) and you should be good to go.Hope that helps,JonOn Wednesday, August 26, 2015 at 9:31:49 PM UTC+1, Julie Reier wrote:I'm hoping that I can get some help with using ansible to manage AWS Windows instances.Firstly, l am new to ansible and Windows systems administration, but I'm pretty good with linux.I am trying to write a playbook that deploys release artifacts to a Windows host. One of the first tasks in the playbook is to remove the Windows instance from a load balancer. I've already had success with removing a Linux instance from a load balancer using ec2_facts action and the ec2_elb module. When I try to run the same tasks with a Windows host, I'm getting this error for ec2_facts: > fatal: [10.200.0.38] => module ec2_facts not found in configured module paths. Additionally, core modules are missing. If this is a checkout, run 'git submodule update --init --recursive' to correct this problem. > > Any advice and guidance will be very much appreciated. Thanks! > > > > >
Thanks Jon. We did try that, but we are still getting the error about ec2_facts not found in configured module paths. Note that the ec2_facts module is found when running for linux hosts. -- 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/loom.20150828T160523-553%40post.gmane.org. For more options, visit https://groups.google.com/d/optout.
