ansible-playbook /etc/ansible/playbooks/uptime-inv-based.yml -i /etc/ansible/playbooks/dc-inv-ALL-vmware.yml
[WARNING]: Failed to load inventory plugin, skipping community.vmware.vmware_vm_inventory
ERROR! No inventory plugins available to generate inventory, make sure you have at least one whitelisted.
Can you check the permission of the /etc/ansible/playbooks/dc-inv-ALL-vmware.yml? if those are only root readable then the non-root users won’t be able to read it and you will get errors.
yes dir are ok as well… see same playbook as soon as i remove the [inventory] section , with user jenkins works well… so something odd here or something really silly
Ansible ships with some plugins that require whitelisting,
Custom plugins should not need this unless plugin author specifies it.
enable callback plugins, they can output to stdout but cannot be ‘stdout’ type.
set plugin path directories here, separate with colons
#action_plugins = /usr/share/ansible/plugins/action #become_plugins = /usr/share/ansible/plugins/become #cache_plugins = /usr/share/ansible/plugins/cache #callback_plugins = /usr/share/ansible/plugins/callback #connection_plugins = /usr/share/ansible/plugins/connection #lookup_plugins = /usr/share/ansible/plugins/lookup
inventory_plugins = /usr/share/ansible/plugins/inventory #vars_plugins = /usr/share/ansible/plugins/vars #filter_plugins = /usr/share/ansible/plugins/filter #test_plugins = /usr/share/ansible/plugins/test #terminal_plugins = /usr/share/ansible/plugins/terminal #strategy_plugins = /usr/share/ansible/plugins/strategy #This option tells Ansible where to cache facts. The value is plugin dependent. #For the jsonfile plugin, it should be a path to a local directory. #For the redis plugin, the value is a host:port:database triplet: fact_caching_connection = localhost:6379:0
What does "doing 744" mean?
If that is meant to be set as permission, then I wonder what you are
trying to do as that is not common for a directories nor for files.
I appreciate your ongoing journey of discovering the world of system
administration.
But instead of frantically trying random things from the internet and
posting the results here, perhaps it's better to ask some senior
colleague for help sorting out the basics first.
BTW your communication style with short message and little context
might be better for the "IRC" medium: https://docs.ansible.com/ansible/latest/community/communication.html#irc-channels