I was having a similar issue with Ansible ping on Vagrant, it just suddenly stuck for no reason and has previously worked absolutely fine. Unlike any other issue like ssh or connective issue, it just forever die with no timeout. One thing I did to resolve this issue is to clean ~/.ansible directory and it … Read more
Update: As of Ansible 2.0, there is now a generic & abstracted package module Usage Examples: Now when the package name is the same across different OS families, it’s as simple as: — – name: Install foo package: name=foo state=latest When the package name differs across OS families, you can handle it with distribution or … Read more
According to the User module you can use this: – name: Adding user {{ user }} user: name={{ user }} group={{ user }} shell=/bin/bash password=${password} groups=sudo append=yes You can just add the groups=groupname and append=yes to add them to an existing user when you’re creating them
Ansible 2.5 comes with special tags never and always. Tag never can be used exactly for this purpose. E.g: tasks: – debug: msg='{{ showmevar}}’ tags: [ ‘never’, ‘debug’ ] In this example, the task will only run when the debug (or never) tag is explicitly requested. [Reference on ansible docs]
You can add following section to your inventory file: [all:vars] ansible_connection=ssh ansible_user=vagrant ansible_ssh_pass=vagrant Note: Before Ansible 2.0 ansible_user was ansible_ssh_user.
You’ve certainly done your research… From all of my experience with ansible what you’re looking to accomplish, isn’t supported. As you mentioned, ansible states that it does not require passwordless sudo, and you are correct, it does not. But I have yet to see any method of using multiple sudo passwords within ansible, without of … Read more
There’s quite a bit about this topic in the documentation: Includes vs. Imports Dynamic vs. Static The main difference is: All import* statements are pre-processed at the time playbooks are parsed. All include* statements are processed as they encountered during the execution of the playbook. So import is static, include is dynamic. From my experience, … Read more
I think you can register the result to a variable, then print with debug. – name: print to stdout command: echo “hello” register: hello – debug: msg=”{{ hello.stdout }}” – debug: msg=”{{ hello.stderr }}”
Try with the option -kK. It will prompt for password. -k, –ask-pass: ask for connection password -K, –ask-become-pass: ask for privilege escalation password
You want the file module. To create a directory, you need to specify the option state=directory : You can see other options at https://docs.ansible.com/ansible/latest/collections/ansible/builtin/file_module.html