ansible-playbook

I want to abort execution of remaining task if certain condition is failed. and display proper error message. So instead of skipping remaining task I want to show error message and stop execution of ansible playbook. Lets say I am running below command $ ansible-playbook playbook.yml -e "param1=value1 param2=value" My playbook look like this:- playbook.yml:- --- - hosts: local user: roop gather_facts: no vars: {param1: "", param2: ""} tasks: #check whether param1 defined - name: 'Check for valid param1' shell: echo {{ param1 }} register: isValidParam1 when: param1 !="" #check if param1 is null

I am trying to write an Ansible playbook that only compiles Nginx if it's not already present and at the current version. However it compiles every time which is undesirable. This is what I have: - shell: /usr/local/nginx/sbin/nginx -v 2>&1 register: nginxVersion - debug: var=nginxVersion - name: install nginx shell: /var/local/ansible/nginx/makenginx.sh when: "not nginxVersion == 'nginx version: nginx/1.8.0'" become: yes The script all works apart from the fact that it runs the shell script every time to compile Nginx. The debug output for nginxVersion is: ok: [server] => { "var": {

When writing and debugging Ansible playbooks, typical workflow is as follows: ansible-playbook ./main.yaml Playbook fails on some task Fix this task and repeat line 1, waiting for all previous tasks to execute again. Which takes a lot of time Ideally, i'd like to resume execution on failed task, having inventory and all facts collected by previous tasks. Is it even possible? How to make playbook writing/debugging faster? Mxx Take a look at http://docs.ansible.com/playbooks_startnstep.html . If you want to start executing your playbook at a particular task, you can do so with the --start-at

I'm designing a kind of playbook lib with individual tasks so in the usual roles repo, I have something like: roles ├── common │ └── tasks │ ├── A.yml │ ├── B.yml │ ├── C.yml │ ├── D.yml │ ├── login.yml │ ├── logout.yml │ └── save.yml ├── custom_stuff_workflow │ └── tasks │ └── main.yml └── other_stuff_workflow └── tasks └── main.yml my main.yml in custom_stuff_workflow then contain something like: --- - include: login.yml - include: A.yml - include: C.yml - include: save.yml - include: logout.yml and this one in the other workflow: --- - include: login.yml - include: B.yml - include: A.yml -

So after reading Ansible docs, I found out that Handlers are only fired when tasks report changes, so for example: some tasks ... notify: nginx_restart # our handler - name: nginx_restart vs some tasks ... register: nginx_restart # do this after nginx_restart changes when: nginx_restart|changed Is there any difference between these 2 methods? When should I use each of them? For me, register seems to have more functionality here, unless I am missing something... There are some differences and which is better depends on the situation. Handlers will only be visible in the output if they have

I'm using the ec2 module with ansible-playbook I want to set a variable to the contents of a file. Here's how I'm currently doing it. Var with the filename shell task to cat the file use the result of the cat to pass to the ec2 module. Example contents of my playbook. vars: amazon_linux_ami: "ami-fb8e9292" user_data_file: "base-ami-userdata.sh" tasks: - name: user_data_contents shell: cat {{ user_data_file }} register: user_data_action - name: launch ec2-instance local_action: ... user_data: "{{ user_data_action.stdout }}" I assume there's a much easier way to do this, but I couldn't find it

I am planning to execute a shell script on a remote server using Ansible playbook. test.sh: touch test.txt Playbook: --- - name: Transfer and execute a script. hosts: server user: test_user sudo: yes tasks: - name: Transfer the script copy: src=test.sh dest=/home/test_user mode=0777 - name: Execute the script local_action: command sudo sh /home/test_user/test.sh When I run the playbook, the transfer successfully occurs but the script is not executed. Pasi H local_action runs the command on the local server, not on the servers you specify in hosts parameter. Change your "Execute the script"

Based on extra vars parameter I Need to write variable value in ansible playbook ansible-playbook playbook.yml -e "param1=value1 param2=value2 param3=value3" If only param1 passed myvariable: 'param1' If only param1,param2 passed myvariable: 'param1,param2' If param1,param2,param3 are passed then variable value will be myvariable: 'param1,param2,param3' When I try to create variable dynamically through template then my playbook always takes previous variable value. But inside dest=roles/myrole/vars/main.yml its writing correct value. What I make a try here - hosts: local user: roop gather