ansible-playbook

I have a situation where I need to check the status of a file on the local machine (the one where I will call ansible-playbook ... ). If a file that is created by the user exists, it needs to be copied over to the remote host(s). If it doesn't exist, then none of the remote hosts need it. I know I've done things like : - name: Check for ~/.blah/config stat: path=/home/ubuntu/.blah/config register: stat_blah_config - name: Do something with blah config shell: ~/do_something_with_config.sh when: stat_aws_config.stat.exists == true But that will only work if the file exists remotely. Is there a

I have a series of numbered files to be processed separately by each server. Each split file made using linux split and then xz compressed to save transfer time. split_001 split_002 split_003 ... split_030 How can I push these files out to a group of 30 servers with ansible? It does not matter which server gets which file so long as they each have a single unique file. I had used a bash file but I am looking for a better solution. Hopefully using ansible. Then I plan to run a shell command to run an at command to start the several hours or days of computation. scp -oStrictHostKeyChecking=no bt

I'm getting a very strange error when I run ansible: GATHERING FACTS *************************************************************** fatal: [i-0f55b6a4] => Could not make dir /$HOME/.ansible/cp: [Errno 13] Permission denied: '/$HOME' TASK: [Task #1] *************************************************************** FATAL: no hosts matched or all hosts have already failed -- aborting PLAY RECAP ******************************************************************** to retry, use: --limit @/home/ubuntu/install.retry i-0f55b6a4 : ok=0 changed=0 unreachable=1 failed=0 Normally, this playbook runs

I'm trying to set up environment specific variables in ansible (e.g. production, staging, development). For some reason, ansible is not picking up variables in group_vars/[environment]. I'm using ansible 1.9.1 Here's a stripped down example of what I'm trying to do. Directory structure: . ├── group_vars │ └── staging ├── hosts │ └── staging └── site.yml group_vars/staging: test_var: "this is a test" site.yml: --- - hosts: localhost tasks: - debug: msg="test variable = {{ test_var }}" hosts/staging is an empty file Output of running ansible-playbook -i hosts/staging site.yml : PLAY [localhost]

Let's assume user01 has two groups defined: groupA and groupB (in addition to the primary group). I can add the account to groupC (ensure user01 belongs to groupC ) using: - user: name=user01 groups=groupC append=yes How can I remove user01 from groupB (ensure user01 does not belong to groupB ) without specifying all the groups the account should belong to? As far as I can tell, you can't with just the normal user module. However, with some fairly crazy gyrations, you can do it in a playbook. I'm not sure I recommend this though; it was just an interesting exercise. (I did test this and it

I have a shell script whose output is an echo of the following format <variable_1>;<variable_2>;<variable_3> etc I want to use these variables and run a mysql query to update a DB like so mysql -u<user> -p<password> -h<host> -e'insert into test_table values ("variable_1","variable_2","variable_3")' My ansible playbook looks like this. --- - hosts: infoServers sudo: yes gather_facts: no tasks: - name: gather info script: get_hostdata.sh register: result - name: print result local_action: command mysql -uuser -ppassword -h192.168.101.10 ansible_db -e'insert into test_table values ("{{ item[0] }}

How can an Ansible playbook loop over a sequence of tasks? I wish to implement a polling loop that executes a task sequence until the task is successful. When it fails, an exception handler will attempt to fix the condition and then the loop will repeat the task sequence. Consider the following imaginary example: - action: - block: - debug: msg='i execute normally' - command: /bin/foo rescue: - debug: msg='I caught an error' - command: /bin/fixfoo always: - debug: msg="this always executes" register: result until: result retries: 5 delay: 10 As of Ansible 2.5, loop is recommended over with