>
> My hunch is that you directory structure is not correct so Ansible can't
> find the files.
>
Yeah, that's what I was thinking too, but unless that changed between
versions I don't know why it would suddenly stop working.
> In the same directory as you inventory file, output of these commands
> would help track it down.
> tree -L 3
>
$ tree -L 3
.
├── ansible.cfg
├── cache
... <REDACTED>
│ ├── server1
│ └── server2
├── examples
│ └── group_vars
│ ├── all
│ └── win
├── filter_plugins
├── group_vars
│ ├── all
│ │ └── all.yaml
│ ├── all.yaml
│ ├── all.yml
│ ├── linux
│ │ └── linux.yaml
│ ├── vagrant_linux.yaml
│ ├── vagrant_win.yaml
│ ├── win
│ │ ├── secure.yaml
│ │ └── win.yaml
│ └── workstations
│ ├── secure.yaml
│ └── workstations.yaml
├── host_vars
│ ├── hostname.yaml
│ └── vagrant2.yaml
├── inventory
│ ├── centos_templates
│ ├── production
│ │ ├── generated
│ │ └── production
│ ├── test
│ ├── vagrant
│ └── workstations
├── library
├── playbooks
│ ├── linux
│ │ ├── linux_ansible_control_machine.yaml
│ │ ├── linux_ftp.yaml
│ │ ├── linux_jump.yaml
│ │ ├── linux_nameservers.yaml
│ │ ├── linux_os_hardening.yaml
│ │ ├── linux_pbis.retry
│ │ ├── linux_pbis.yaml
│ │ ├── linux.retry
│ │ ├── linux_set_root_password.yaml
│ │ ├── linux_utility.yaml
│ │ ├── linux_webservers.yaml
│ │ ├── linux.yaml
│ │ └── templates
│ ├── testing
│ │ ├── dumpall.j2
│ │ ├── dump_vars.yaml
│ │ └── vagrant.yaml
│ ├── win
│ │ └── win_servers.yaml
│ └── workstations
│ └── win_workstations.yaml
├── README.md
├── roles
│ ├── linux-ansible-user
│ │ ├── defaults
│ │ ├── files
│ │ ├── handlers
│ │ ├── meta
│ │ ├── tasks
│ │ ├── templates
│ │ └── vars
│ ├── linux-common
│ │ ├── defaults
│ │ ├── files
│ │ ├── handlers
│ │ ├── tasks
│ │ ├── templates
│ │ └── vars
│ ├── linux-pbis
│ │ ├── defaults
│ │ ├── files
│ │ ├── meta
│ │ ├── tasks
│ │ ├── templates
│ │ └── vars
│ ├── linux-sendmail-client
│ │ ├── defaults
│ │ ├── files
│ │ ├── handlers
│ │ ├── meta
│ │ ├── tasks
│ │ ├── templates
│ │ └── vars
│ ├── linux-set-root-password
│ │ └── tasks
│ ├── linux-sudoers
│ │ ├── defaults
│ │ ├── files
│ │ ├── handlers
│ │ ├── meta
│ │ ├── tasks
│ │ ├── templates
│ │ └── vars
├── scripts
│ ├── ad_kerberos
│ ├── Gemfile
│ ├── Gemfile.lock
│ └── windows-servers.rb
├── site.retry
├── site.yaml
└── Vagrantfile
I have removed a lot of unnecessary output from the above, but it should
still show the required hierarchy. The group_vars/all.y{,a}ml are an exact
copy of group_vars/all/all.yaml and were created only for testing.
> ansible --version
>
$ ansible --version
ansible 2.3.0 (devel 92a568c816) last updated 2017/01/20 13:14:32 (GMT -600)
config file =
configured module search path = Default w/o overrides
>
> But also your original message you wrote this
> "I've recently updated from Ansible 2.1 to the latest (using git pull),
> which
> may or may not have been when this issue started."
>
> It you didn't remove 2.1 completely before you install from source you
> may have a combination of the two, and that will give you some strange
> behaviors.
>
Unfortunately I don't think that's the case. I moved our ansible_source
directory aside and cloned the ansible repo again from scratch — there
should not be any conflicts.
Thanks for the reply, and any additional help!
--
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/86ebaa80-d5bc-42ee-a879-d226d2e20364%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
