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...

Ansible Handler notify vs register

I want to evaluate multiple condition in ansible using when, here is my playbook:

    - name: Check that the SSH Key exists
       local_action:
         module: stat
         path: &quot;/home/{{ login_user.stdout }}/{{ ssh_key_location }}&quot;
       register: sshkey_result
    
     - name: Generating a new SSH key for the current user it&#39;s not exists already
       local_action:
          module: user
          name: &quot;{{ login_user.stdout }}&quot;
          generate_ssh_key: yes 
          ssh_key_bits: 2048
       when: sshkey_result.rc == 1 and  ( github_username is undefined or github_username |lower == &#39;none&#39; )

here is my var file for reference:

    ---
    vpc_region: eu-west-1
    key_name: my_github_key
    ssh_key_location: .ssh/id_rsa.pub

When I try to execute this playbook, I am getting this error:

    TASK: [test | Check that the SSH Key exists] **********************************
    ok: [localhost -&gt; 127.0.0.1]
        
     TASK: [test | Generating a new SSH key for the current user it&#39;s not exists already] ***
     fatal: [localhost] =&gt; error while evaluating conditional: sshkey_result.rc == 1 and  ( github_username is undefined or github_username |lower == &#39;none&#39; )
            
            FATAL: all hosts have already failed -- aborting

Can somebody point me out that how we can use multiple conditions with ansible on single task.

Thanks








Checking for multiple conditions using &quot;when&quot; on single task in ansible

I am using ansible to script a deployment for an API.  I would like this to work sequentially through each host in my inventory file so that I can fully deploy to one machine at a time.

With the out box behaviour, each task in my playbook is executed for each host in the inventory file before moving on to the next task.

How can I change this behaviour to execute all tasks for a host before starting on the next host? Ideally I would like to only have one playbook.

Thanks

Ansible - How to sequentially execute playbook for each host

Is there a way to check playbook syntax and variables?

I&#39;m trying to dry-run(--check) but for some reasons it works really slow. It looks like it tries to perform an action instead of just check the syntax

I want to omit en errors like this:

    ...&quot;msg&quot;: &quot;AnsibleUndefinedVariable: ERROR! &#39;application_name&#39; is undefined&quot;}

Ansible. Fast way to check syntax?

In Ansible 1.7, I can use --tags from the command-line to only run a subset of that playbooks tasks. 

But I&#39;m wanting to bake into my playbook to run a set of roles with only tasks that match tags. That is, I don&#39;t want to have to pass this in via the command-line since it will be the same every time. 

At first I thought it was this command, but this does the opposite: tagging tasks with these tags instead of filtering them out based on this. 

    roles:
      - { role: webserver, port: 5000, tags: [ &#39;web&#39;, &#39;foo&#39; ] }

I can imagine implementing this using conditionals but tags would be a much more elegant way of achieving this.

Ansible: In a playbook, filter a role by tag(s) without passing at the command-line

I&#39;m running Ansible playbook and it works fine on one machine. 

On a new machine when I try for the first time, I get the following error.

    17:04:34 PLAY [appservers] ************************************************************* 
    17:04:34 
    17:04:34 GATHERING FACTS *************************************************************** 
    17:04:34 fatal: [server02.cit.product-ref.dev] =&gt; {&#39;msg&#39;: &quot;FAILED: (22, &#39;Invalid argument&#39;)&quot;, &#39;failed&#39;: True}
    17:04:34 fatal: [server01.cit.product-ref.dev] =&gt; {&#39;msg&#39;: &quot;FAILED: (22, &#39;Invalid argument&#39;)&quot;, &#39;failed&#39;: True}
    17:04:34 
    17:04:34 TASK: [common | remove old ansible-tmp-*] ************************************* 
    17:04:34 FATAL: no hosts matched or all hosts have already failed -- aborting
    17:04:34 
    17:04:34 
    17:04:34 PLAY RECAP ******************************************************************** 
    17:04:34            to retry, use: --limit @/var/lib/jenkins/site.retry
    17:04:34 
    17:04:34 server01.cit.product-ref.dev      : ok=0    changed=0    unreachable=1    failed=0   
    17:04:34 server02.cit.product-ref.dev      : ok=0    changed=0    unreachable=1    failed=0   
    17:04:34 
    17:04:34 Build step &#39;Execute shell&#39; marked build as failure
    17:04:34 Finished: FAILURE

This error can be resolved, if I first go to the source machine (from where I&#39;m running the ansible playbook) and manually ssh to the target machine (as the given user) and enter &quot;yes&quot; for known_hosts file entry.

Now, if I run the same ansible playbook second time, it works without an error.

Therefore, how can I suppress the prompt what SSH gives while making ssh known_hosts entry for the first time for a given user (~&lt;user&gt;/.ssh folder, file known_hosts)?

I found I can do this if I use the following config entries in **~/.ssh/config** file.

~/.ssh/config


    # For vapp virtual machines
    Host *
      StrictHostKeyChecking no
      UserKnownHostsFile=/dev/null
      User kobaloki
      LogLevel ERROR

i.e. if I place the above code in the user&#39;s ~/.ssh/config file of a remote machine and try Ansible playbook for the first time, I won&#39;t be prompted for entring &quot;yes&quot; and playbook will run successfully (without requiring the user to manually create a known_hosts file entry from the source machine to the target/remote machine).

My questions:
1. What security issues I should take care if I go ~/.ssh/config way
2. How can I pass the settings (what&#39;s there in the config file) as parameters/options to ansible at command line so that it will run first time on a new machine (without prompting / depending upon the known_hosts file entry on the source machine for the target machine?





ansible ssh prompt known_hosts issue

I have an Ansible playbook for deploying a Java app as an init.d daemon.

Being a beginner in both Ansible and Linux I&#39;m having trouble to conditionally execute tasks on a host based on the host&#39;s status.

Namely I have some hosts having the service already present and running where I want to stop it before doing anything else. And then there might be new hosts, which don&#39;t have the service yet. So I can&#39;t simply use `service: name={{service_name}} state=stopped`, because this will fail on new hosts.

How I can I achieve this? Here&#39;s what I have so far:
  

      - name: Check if Service Exists
        shell: &quot;if chkconfig --list | grep -q my_service;   then echo true;   else echo false; fi;&quot;
        register: service_exists
    
    # This should only execute on hosts where the service is present
      - name: Stop Service
        service: name={{service_name}} state=stopped
        when: service_exists
        register: service_stopped
    
    # This too
      - name: Remove Old App Folder
        command: rm -rf {{app_target_folder}}
        when: service_exists

    # This should be executed on all hosts, but only after the service has stopped, if it was present
      - name: Unpack App Archive
        unarchive: src=../target/{{app_tar_name}} dest=/opt



Check if service exists with Ansible

I need to create new variable from contents of other variables. Currently I&#39;m using something like this:

    - command: echo &quot;{{ var1 }}-{{ var2 }}-{{ var3 }}&quot;
      register: newvar

The problem is:
 
- Usage of `{{ var1 }}...{{ varN }}` brings too long strings and very ugly code.
- Usage of `{{ newvar.stdout }}` a bit better but confusing.
- Usage of `set_fact` module caches *fact* between runs. It isn&#39;t appropriate for me.

Is there any other solution?

Proper way to concatenate variable strings

I generate files with ansible on remote host and after this generation, I would like to read theses files in another task.

I don&#39;t find any module to read remote file with ansible (lookup seems only on local host).

Do you know a module like this ?

Thanks

**EDIT:**

Here is my use case:

I generate ssh keys and I add it to github. These keys are setting by an object in var files so I loop like this to generate it:

        tasks:
      - name: Create ssh key
        user:
          name: &quot;{{sshConfigFile.user}}&quot;
          generate_ssh_key: yes
          ssh_key_file: &quot;.ssh/{{item.value.file}}&quot;
          state: present
        with_dict: &quot;{{sshConfiguration}}&quot;

It works very fine but how read these keys to send it to github via the API ?

Ansible: read remote file

I am getting this error in my `nginx-error.log` file:

    2014/02/17 03:42:20 [crit] 5455#0: *1 connect() to unix:/tmp/uwsgi.sock failed (13: Permission denied) while connecting to upstream, client: xx.xx.x.xxx, server: localhost, request: &quot;GET /users HTTP/1.1&quot;, upstream: &quot;uwsgi://unix:/tmp/uwsgi.sock:&quot;, host: &quot;EC2.amazonaws.com&quot;

The browser also shows a 502 Bad Gateway Error. The output of a `curl` is the same, Bad Gateway html

I&#39;ve tried to fix it by changing permissions for `/tmp/uwsgi.sock` to 777. That didn&#39;t work. I also added myself to the `www-data` group (a couple questions that looked similar suggested that). Also, no dice. 

Here is my `nginx.conf` file:

**nginx.conf**

    worker_processes 1;
    worker_rlimit_nofile 8192;

    events {
      worker_connections  3000; 
    }

    error_log  /var/log/nginx/error.log warn;
    pid        /var/run/nginx.pid;

    http {
        include       /etc/nginx/mime.types;
        default_type  application/octet-stream;

        log_format  main  &#39;$remote_addr - $remote_user [$time_local] &quot;$request&quot; &#39;
                      &#39;$status $body_bytes_sent &quot;$http_referer&quot; &#39;
                      &#39;&quot;$http_user_agent&quot; &quot;$http_x_forwarded_for&quot;&#39;;

        access_log  /var/log/nginx/access.log  main;

        sendfile        on; 
        #tcp_nopush     on; 

        keepalive_timeout  65; 

        #gzip  on; 

        include /etc/nginx/conf.d/*.conf;
        include /etc/nginx/sites-enabled/*;
    }


I am running a Flask application with Nginsx and Uwsgi, just to be thorough in my explanation. If anyone has any ideas, I would really appreciate them.

------------
**EDIT**

I have been asked to provide my uwsgi config file. So, I never personally wrote my nginx or my uwsgi file. I followed the guide [here][1] which sets everything up using ansible-playbook. The `nginx.conf` file was generated automatically, but there was nothing in `/etc/uwsgi` except a `README` file in both `apps-enabled` and `apps-available` folders. Do I need to create my own config file for uwsgi? I was under the impression that ansible took care of all of those things. 

I believe that `ansible-playbook` figured out my uwsgi configuration since when I run this command

    uwsgi -s /tmp/uwsgi.sock -w my_app:app

it starts up and outputs this:

    *** Starting uWSGI 2.0.1 (64bit) on [Mon Feb 17 20:03:08 2014] ***
    compiled with version: 4.7.3 on 10 February 2014 18:26:16
    os: Linux-3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014
    nodename: ip-10-9-xxx-xxx
    machine: x86_64
    clock source: unix
    detected number of CPU cores: 1
    current working directory: /home/username/Project
    detected binary path: /usr/local/bin/uwsgi
    !!! no internal routing support, rebuild with pcre support !!!
    *** WARNING: you are running uWSGI without its master process manager ***
    your processes number limit is 4548
    your memory page size is 4096 bytes
    detected max file descriptor number: 1024
    lock engine: pthread robust mutexes
    thunder lock: disabled (you can enable it with --thunder-lock)
    uwsgi socket 0 bound to UNIX address /tmp/uwsgi.sock fd 3
    Python version: 2.7.5+ (default, Sep 19 2013, 13:52:09)  [GCC 4.8.1]
    *** Python threads support is disabled. You can enable it with --enable-threads ***
    Python main interpreter initialized at 0x1f60260
    your server socket listen backlog is limited to 100 connections
    your mercy for graceful operations on workers is 60 seconds
    mapped 72760 bytes (71 KB) for 1 cores
    *** Operational MODE: single process ***
    WSGI app 0 (mountpoint=&#39;&#39;) ready in 3 seconds on interpreter 0x1f60260 pid: 26790 (default app)
    *** uWSGI is running in multiple interpreter mode ***
    spawned uWSGI worker 1 (and the only) (pid: 26790, cores: 1)


  [1]: http://mattupstate.com/python/devops/2012/08/07/flask-wsgi-application-deployment-with-ubuntu-ansible-nginx-supervisor-and-uwsgi.html

Nginx error: (13: Permission denied) while connecting to upstream

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 &quot;param1=value1 param2=value&quot;
   
   
My playbook look like this:-

**playbook.yml:-**

	---
		- hosts: local
		  user: roop
		  gather_facts: no
		 
	      vars: {param1: &quot;&quot;, param2: &quot;&quot;}
		 
		  tasks:

			#check whether param1 defined
			- name: &#39;Check for valid param1&#39;
			  shell: echo {{ param1 }}
			  register: isValidParam1
			  when: param1 !=&quot;&quot;

			#check if param1 is null or invalid  
			- name: &#39;check if param1 is null or invalid&#39; 
			  debug: msg=&quot;Please enter correct param1&quot;
			  when: param1 == &quot;&quot;
			  
			#check whether param2 defined
			- name: &#39;Check for valid param2&#39;
			  shell: echo {{ param2 }}
			  register: isValidParam2
			  when: param2 != &quot;&quot;

			#check if param2 is null or invalid  
			- name: &#39;check if param2 is null or invalid&#39; 
			  debug: msg=&quot;Please enter correct param2&quot;
			  when: param2 == &quot;&quot;  
			  
			  
			#check params is valid and defined
			- name: &#39;Check for valid params&#39;
			  shell: echo &quot;param1={{ param1 }} param2={{ param2 }}
			  register: validParams
			  when: isValidParam1 is defined and isValidParam2 is defined
			  
			#check if params are invalid then abort below all tasks.  
			- name: &#39;check if validParams is null or invalid&#39; 
			  debug: msg=&quot;Please enter correct Params&quot;
			  when: validParams is not defined    
			  

             # based on validParams, and different value of param1 more than 
              10 task executing.
			
			
As I have mentioned in my last task comment. I am executing more than 10 task based on `validParams` and `param1` different value. What I need here 
if `validParams` is undefined then abort all execution and show error messages.

Is there any efficient way to do this . Please suggest me. 


Abort execution of remaining task if certain condition is failed

I&#39;m new to ansible and wonder how to do so as the following didn&#39;t work

    ansible-playbook -i &#39;10.0.0.1,&#39; yada-yada.yml --tags &#39;loaddata&#39; django_fixtures=&quot;tile_colors&quot;

Where `django_fixtures` is my variable.

How can I pass variable to ansible playbook in the command line?

I&#39;m using Ansible for some simple user management tasks with a small group of computers. Currently, I have my playbooks set to `hosts: all` and my hosts file is just a single group with all machines listed:

    # file: hosts
    [office]
    imac-1.local
    imac-2.local
    imac-3.local

I&#39;ve found myself frequently having to target a single machine. The `ansible-playbook` command can limit plays like this:

    ansible-playbook --limit imac-2.local user.yml

But that seems kind of fragile, especially for a potentially destructive playbook. Leaving out the `limit` flag means the playbook would be run everywhere. Since these tools only get used occasionally, it seems worth taking steps to foolproof playback so we don&#39;t accidentally nuke something months from now.

Is there a best practice for limiting playbook runs to a single machine? Ideally the playbooks should be harmless if some important detail was left out.



Safely limiting Ansible playbooks to a single machine?

I&#39;m running into an error I&#39;ve never seen before. Here is the command and the error:

    $ ansible-playbook create_api.yml
    
    PLAY [straw] ******************************************************************
    
    GATHERING FACTS ***************************************************************
    failed: [104.55.47.224] =&gt; {&quot;failed&quot;: true, &quot;parsed&quot;: false}
    /bin/sh: 1: /usr/bin/python: not found
    
    
    TASK: [typical | install required system packages] *****************************
    FATAL: no hosts matched or all hosts have already failed -- aborting
    
    
    PLAY RECAP ********************************************************************
               to retry, use: --limit @/Users/john/create_api.retry
    
    104.55.47.224               : ok=0    changed=0    unreachable=0    failed=1


Here is the create_api.yml file:

    ---
    
    - hosts: api
      remote_user: root
      roles:
        - api

And here is the hosts file:

    [api]
    104.55.47.224


I can remove the roles section and it won&#39;t make it to the first TASK, it will instead make it will only make it to the line `/bin/sh: 1: /usr/bin/python: not found`. What could be going on here? 

---
*NOTE:* In case anyone is pinging the IP address and failing to get a response, you should know I&#39;ve changed the IP address since pasting code.

**EDIT**
python was installed locally, the problem was that it was not installed on the remote machine, which was running Ubuntu 15.04

Ansible fails with /bin/sh: 1: /usr/bin/python: not found

All my Ansible playbooks/roles are checked in to my git repo.

However, for Ansible Galaxy roles I always have to explicitly download them one by one on every machine I want to run Ansible from.

It&#39;s even tough to know in advance exactly which Ansible Galaxy roles are needed until Ansible complains about a missing role at runtime.

How is one supposed to manage the Ansible Galaxy role dependencies? I would like to either have them checked into my git repo along with the rest of my ansible code or have them automatically be identified and downloaded when I run Ansible on a new machine.

How to automatically install Ansible Galaxy roles?

I am looking for a way to perform a task when ansible variable is not registers /undefined e.g 

    -- name: some task
       command:  sed -n &#39;5p&#39; &quot;{{app.dirs.includes}}/BUILD.info&quot; | awk &#39;{print  $2}&#39;
       when: (! deployed_revision) AND ( !deployed_revision.stdout )
       register: deployed_revision





How to run a task when variable is undefined in ansible?

This is a fragment of a playbook that I&#39;m using (`server.yml`):

    - name: Determine Remote User
      hosts: web
      gather_facts: false
      roles:
        - { role: remote-user, tags: [remote-user, always] }

My hosts file has different groups of servers, e.g.

    [web]
    x.x.x.x

    [droplets]
    x.x.x.x

Now I want to execute `ansible-playbook -i hosts/&lt;env&gt; server.yml` and override `hosts: web` from `server.yml` to run this playbook for `[droplets]`.

Can I just override as a one time off thing, without editing `server.yml` directly?

Thanks.

Override hosts variable of Ansible playbook from the command line

I am pulling JSON via the URI module and want to write the received content out to a file.  I am able to get the content and output it to the debugger so I know the content has been received, but I do not know the best practice for writing files.

Write variable to a file in Ansible

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

Ansible: Set variable to file content

Inside my playbook I&#39;d like to create a variable holding the output of an external command. Afterwards I want to make use of that variable in a couple of templates.  

Here are the relevant parts of the playbook:

      tasks:
        - name: Create variable from command
          command: &quot;echo Hello&quot;
          register: command_output
        - debug: msg=&quot;{{command_output.stdout}}&quot;
        
        - name: Copy test service
          template: src=../templates/test.service.j2 dest=/tmp/test.service
        - name: Enable test service
          shell: systemctl enable /tmp/test.service
        - name: Start test service
          shell: systemctl start test.service


and let&#39;s say this is my template:

    [Unit]
    Description=MyApp
    After=docker.service
    Requires=docker.service
    
    [Service]
    TimeoutStartSec=0
    ExecStartPre=-/usr/bin/docker kill busybox1
    ExecStartPre=-/usr/bin/docker rm busybox1
    ExecStartPre=/usr/bin/docker pull busybox
    ExecStart=/usr/bin/docker run --name busybox1 busybox /bin/sh -c &quot;while true; do echo {{ string_to_echo }}; sleep 1; done&quot;
    
    [Install]
    WantedBy=multi-user.target

(Notice the `{{ string_to_echo }}`)


So what I&#39;m basically looking for is a way to store the contents of `command_output.stdout` (which is generated/retrieved during the first task) in a new variable `string_to_echo`.    
That variable I&#39;d like to use in multiple templates afterwards.  

I guess I could just use `{{command_output.stdout}}` in my templates, but I want to get rid of that `.stdout` for readability.

Ansible: Store command&#39;s stdout in new variable?

I have a copy task inside a role and I was expecting that the `src` location would be relative to the role itself, not the playbook that calls the roles.

How do I make this work and use the files from `myfrole/files` from a task inside `myrole/tasks`, I don&#39;t want to include the role name as part of the path as it does not make much sense. If I do it will break if I duplicate the role.

How to copy files with ansible relatively to the role?

I have multiple tasks depend from the value of variable1. I want to check if the value is in {{variable1}} but i got an error:

    - name: do something when the value in variable1
      command: &lt;command&gt;
      when: &quot;&#39;value&#39; in {{variable1}}&quot;

I&#39;m using ansible 2.0.2 

Run an Ansible task only when the variable contains a specific string

I have taken over a Ubuntu 14.04 server. It has a user called &quot;deployer&quot; (used with capistrano), and as such, it needs sudo privileges. With this setup, I can log into the server and do stuff like:

    workstation&gt; ssh deployer@myserver
    myserver&gt;  sudo apt-get install git
    myserver&gt; exit
    workstation&gt;

I am trying to figure out how to use Ansible (version 2.0.2.0 and python 2.7.3) to create a user called &quot;deployer&quot; and be able to log into the server with that id and then so sudo-ish things like &quot;apt-get install&quot;. My playbook looks like this:

    ---
    - hosts: example
      become: yes
      tasks:
      - name: Update apt cache
        apt:
          update_cache: yes
          cache_valid_time: 3600

      - group: name=sudo state=present

      - name: Add deployer user and add it to sudo
        user: name=deployer
              state=present
              createhome=yes
        become: yes
        become_method: &quot;sudo&quot;

      - name: Set up authorized keys for the deployer user
        authorized_key: user=deployer key=&quot;{{item}}&quot;
        with_file:
          - /home/jaygodse/.ssh/id_rsa.pub



After running this playbook, I am able to ssh into the machine as &quot;deployer&quot;, (e.g. ssh deployer@myserver) but if I run a sudo command, it always asks me for my sudo password. 

I understand that the &quot;deployer&quot; user ultimately has to find its way into the visudo users file, but I cannot figure out which magical Ansible incantations to invoke so that I can ssh into the machine as  deployer and then run a sudo command (e.g. sudo apt-get install git&quot;) without being prompted for a sudo  password. 

I have searched high and low, and I can&#39;t seem to find an Ansible playbook fragment which puts the user &quot;deployer&quot; into the sudo group without requiring a password.  How is this done?

Ansible: create a user with sudo privileges

I&#39;m designing a kind of playbook lib with individual tasks

so in the usual roles repo, I have something like:

    roles
    ├── common
    │&#160;&#160; └── tasks
    │       ├── A.yml
    │&#160;&#160;     ├── B.yml
    │       ├── C.yml
    │       ├── D.yml
    │       ├── login.yml
    │       ├── logout.yml
    │&#160;&#160;     └── 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
    - include: D.yml
    - include: save.yml
    - include: logout.yml
I can&#39;t find a way to do it in a natural way:
one way that worked was having all tasks in a single role and tagging the relevant tasks while including a custom_stuff_workflow

The problem I have with that is that tags cannot be set in the calling playbook: it&#39;s only to be set at command line
as I&#39;m distributing this ansible repo with many people in the company, I can&#39;t rely on command line invocations (it would be nice to have a `#!` header in yml to be processed by `ansible-playbook` command)

I could also copy the relevant tasks (inside common in the above tree) in each workflow, but I don&#39;t want to repeat them around

Can someone see a solution to achieve what I&#39;d like without repeating the tasks over different roles?

I guess the corner stone of my problem is that I define tasks as individual and it looks not natural in ansible...


Thanks a lot

PS: note that the tasks in the workflow have to be done in specific order and the only natural steps to abstract would be the login and save/logout

PPS: I&#39;ve seen this question https://stackoverflow.com/questions/22078333/how-do-i-call-a-role-from-within-another-role-in-ansible but it does not solve my problem as it&#39;s invoking a full role and not a subset of the tasks in a role

include tasks from another role in ansible playbook

I&#39;m trying to use Ansible to run the following two commands:

`sudo apt-get update &amp;&amp; sudo apt-get upgrade -y`

I know with ansible you can use: 

`ansible all -m shell -u user -K -a &quot;uptime&quot;`

Would running the following command do it? Or do I have to use some sort of `raw` command

`ansible all -m shell -u user -K -a &quot;sudo apt-get update &amp;&amp; sudo apt-get upgrade -y&quot;`



How to run apt update and upgrade via Ansible shell

# The settings
Consider an [Ansible inventory file][1] similar to the following example:

    [san_diego]
    host1
    host2
    
    [san_francisco]
    host3
    host4
    
    [west_coast]
    san_diego
    san_francisco
    
    [west_coast:vars]
    db_server=foo.example.com
    db_host=5432
    db_password=top secret password

# The problem

I would like to store some of the vars (like `db_password`) in an [Ansible vault][2], but not the entire file.

How can a vault-encrypted ansible file be imported into an unencrypted inventory file?

# What I&#39;ve tried

I have created an encrypted vars file and tried importing it with:

    include: secrets

To which `ansible-playbook` responded with:

    ERROR: variables assigned to group must be in key=value form

Probably because it tried to parse the `include` statement as a variable.

  [1]: http://docs.ansible.com/intro_inventory.html
  [2]: https://docs.ansible.com/playbooks_vault.html

Ansible: How to encrypt some variables in an inventory file in a separate vault file?

Can I notify the handler in another role?  What should I do to make ansible find it?

The use case is, e.g. I want to configure some service and then restart it if changed.  Different OS have probably different files to edit and even the file format can be different.  So I would like to put them into different roles (because the file format can be different, it can&#39;t be done by setting group_vars).  But the way to restart the service is the same, using `service` module; so I&#39;d like to put the handler to `common` role.

Is anyway to achieve this?  Thanks.

Ansible notify handlers in another role

In Ansible (1.9.4) or 2.0.0

I ran the following action:

    - debug: msg=&quot;line1 \n {{ var2 }} \n line3 with var3 = {{ var3 }}&quot;


**$ cat roles/setup_jenkins_slave/tasks/main.yml**

    - debug: msg=&quot;Installing swarm slave = {{ slave_name }} at {{ slaves_dir }}/{{ slave_name }}&quot;
      tags:
        - koba
    
    - debug: msg=&quot;1 == Slave properties = fsroot[ {{ slave_fsroot }} ], master[ {{ slave_master }} ], connectingToMasterAs[ {{ slave_user }} ], description[ {{ slave_desc }} ], No.Of.Executors[ {{ slave_execs }} ], LABELs[ {{ slave_labels }} ], mode[ {{ slave_mode }} ]&quot;
      tags:
        - koba
    
    
    - debug: msg=&quot;print(2 == Slave properties = \n\nfsroot[ {{ slave_fsroot }} ],\n master[ {{ slave_master }} ],\n connectingToMasterAs[ {{ slave_user }} ],\n description[ {{ slave_desc }} ],\n No.Of.Executors[ {{ slave_execs }} ],\n LABELs[ {{ slave_labels }} ],\n mode[ {{ slave_mode }} ])&quot;
      tags:
        - koba

But this is not printing the variable with new lines (for the 3rd debug action)?




Ansible - Print message - debug: msg=&quot;line1 \n {{ var2 }} \n line3 with var3 = {{ var3 }}&quot;

I am using Ansible to deploy my project and I trying to check if an specified package is installed, but I have a problem with it task, here is the task:

    - name: Check if python-apt is installed
      command: dpkg -l | grep python-apt
      register: python_apt_installed
      ignore_errors: True

And here is the problem:

    $ ansible-playbook -i hosts idempotent.yml
    
    PLAY [lxc-host] *************************************************************** 
    
    GATHERING FACTS *************************************************************** 
    ok: [10.0.3.240]
    
    TASK: [idempotent | Check if python-apt is installed] ************************* 
    failed: [10.0.3.240] =&gt; {&quot;changed&quot;: true, &quot;cmd&quot;: [&quot;dpkg&quot;, &quot;-l&quot;, &quot;|&quot;, &quot;grep&quot;, &quot;python-apt&quot;], &quot;delta&quot;: &quot;0:00:00.015524&quot;, &quot;end&quot;: &quot;2014-07-10 14:41:35.207971&quot;, &quot;rc&quot;: 2, &quot;start&quot;: &quot;2014-07-10 14:41:35.192447&quot;}
    stderr: dpkg-query: error: package name in specifier &#39;|&#39; is illegal: must start with an alphanumeric character
    ...ignoring
    
    PLAY RECAP ******************************************************************** 
    10.0.3.240                 : ok=2    changed=1    unreachable=0    failed=0 

Why is illegal this character **&#39;|&#39;** . 


Ansible Command module says that &#39;|&#39; is illegal character

Sometimes I need to test some jinja2 templates that I use in my ansible roles. What is the simplest way for doing this?

For example, I have a template (test.j2):

    {% if users is defined and users %}
    {% for user in users %}{{ user }}
    {% endfor %}
    {% endif %}
and vars (in group_vars/all):

    ---
    users:
      - Mike
      - Smith
      - Klara
      - Alex


How can I test jinja2 templates in ansible?

When writing and debugging Ansible playbooks, typical workflow is as follows:

1. `ansible-playbook ./main.yaml`
2. Playbook fails on some task
3. Fix this task and repeat line 1, waiting for all previous tasks to execute again. Which takes a lot of time

Ideally, i&#39;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?

How to continue execution on failed task after fixing error in playbook?

I am learning Ansible. I have a playbook to clean up resources, and I want the playbook to ignore every error and keep going on till the end , and then fail at the end if there were errors.

I can ignore errors with

      ignore_errors: yes

If it was one task, I could do something like ( from ansible error catching)

    - name: this command prints FAILED when it fails
      command: /usr/bin/example-command -x -y -z
      register: command_result
      ignore_errors: True
    
    - name: fail the play if the previous command did not succeed
      fail: msg=&quot;the command failed&quot;
      when: &quot;&#39;FAILED&#39; in command_result.stderr&quot;


How do I fail at the end ? I have several tasks, what would my &quot;When&quot; condition be?



Ansible Ignore errors in tasks and fail at end of the playbook if any tasks had errors

I&#39;m writing an Ansible playbook and have a task which will always fail in check mode:

    hosts: ...
    tasks:
        - set_fact: filename=&quot;{{ansible_date_time.iso8601}}&quot;
        - file: state=touch name={{filename}}
        - file: state=link src={{filename}} dest=latest

In check mode, the file will not be created so the `link` task will always fail.  Is there a way to mark such a task to be skipped when running in check mode?  Something like:

    - file: state=link src={{filename}} dest=latest
      when: not check_mode

Skip Ansible task when running in check mode?

Recently I started digging into Ansible and writing my own playbooks. However, I have a troubles with understanding difference between `become` and `become_user`. 
As I understand it `become_user` is something similar to `su &lt;username&gt;`, and `become` means something like `sudo su` or &quot;perform all commands as a sudo user&quot;. But sometimes these two directives are mixed. 

Could you explain the correct meaning of them?

Difference between become and become_user in Ansible

Some of tasks I wrote start and never end. Ansible does not provide any errors or logs that would explain this, even with -vvvv option. Playbook just hangs and passing hours doesn&#39;t change anything.

When I try to run my tasks manually (by entering commands via SSH) everything is fine. 

Example task that hangs:

    - name: apt upgrade
      shell: apt-get upgrade

Is there any way to see stdout and stderr ? I tried:

    - name: apt upgrade
      shell: apt-get upgrade
      register: hello
    - debug: msg=&quot;{{ hello.stdout }}&quot;
    - debug: msg=&quot;{{ hello.stderr }}&quot;

but nothing changed.

I do have required permissions and I pass correct sudo password - other tasks that require sudo execute correctly.

How to detect why Ansible playbook hangs during execution

How can I pass yaml array to `--extra-vars` in Ansible playbook. Ansible documentation does not declares its syntax nor I can find that on any internet resource.

I mean if I have a playbook:

    ---
      - hosts: {{hostName}}
      - remote_user: admin
      ...
Then I should call my playbook like

`ansible-playbook DeployWar.yml --extra-vars=&quot;hostName=tomcat-webApp&quot;`

But I want to run this playbook on two servers say `tomcat-webApp` and `tomcat-all`, and I want to control it from out side i.e. using `--extra-vars`. What I have tried to do is:

    ansible-playbook DeployWar.yml --extra-vars=&quot;hostName=[tomcat-webApp, tomcat-all]&quot;

    ansible-playbook DeployWar.yml --extra-vars=&quot;hostName={tomcat-webApp, tomcat-all}&quot;

    ansible-playbook DeployWar.yml --extra-vars=&quot;[{hostName: tomcat-webApp}, {hostName: tomcat-all}]&quot;

But in all cases playbook fails declaring a syntax error in my call.
Any help appreciated.

Pass array in --extra-vars - Ansible

Let&#39;s imagine an inventory file like this:  

    node-01 ansible_ssh_host=192.168.100.101
    node-02 ansible_ssh_host=192.168.100.102
    node-03 ansible_ssh_host=192.168.100.103
    node-04 ansible_ssh_host=192.168.100.104
    node-05 ansible_ssh_host=192.168.100.105
    
    [mainnodes]
    node-[01:04]

In my playbook I now want to create some variables containing the IP addresses of the group `mainnodes`:  

    vars:
      main_nodes_ips: &quot;192.168.100.101,192.168.100.102,192.168.100.103,192.168.100.104&quot;
      main_nodes_ips_with_port: &quot;192.168.100.101:3000,192.168.100.102:3000,192.168.100.103:3000,192.168.100.104:3000&quot;

This is what I got so far:

    vars:
      main_nodes_ips: &quot;{{groups[&#39;mainnodes&#39;]|join(&#39;,&#39;)}}&quot;
      main_nodes_ips_with_port: &quot;{{groups[&#39;mainnodes&#39;]|join(&#39;:3000,&#39;)}}&quot;

but that would use the host names instead of the IP addresses. 

Any ideas how this could be done?

**Update**:

looking at the docs for a while, I think this would allow me to loop through all the ip adresses:

    {% for host in groups[&#39;mainnodes&#39;] %}
        {{hostvars[host][&#39;ansible_ssh_host&#39;]}}
    {% endfor %}

But I just can&#39;t figure out how to create an array that holds all these IPs. So that I can use the `|join()` command on them.

**Update2:**  
I just thought I had figured it out... but it turns out that you cannot use the {% %} syntax in the playbook... or can I?
Well in the vars section it didn&#39;t. :/

    vars:
      {% set main_nodes_ip_arr=[] %}
      {% for host in groups[&#39;mesos-slave&#39;] %}
         {% if main_nodes_ip_arr.insert(loop.index,hostvars[host][&#39;ansible_ssh_host&#39;]) %} {% endif %}
      {% endfor %}
      main_nodes_ips: &quot;{{main_nodes_ip_arr|join(&#39;,&#39;)}}&quot;
      main_nodes_ips_with_port: &quot;{{main_nodes_ip_arr|join(&#39;:3000,&#39;)}}&quot;

Ansible: Get all the IP addresses of a group

How would I save a registered Variable to a file? I took this from the [tutorial][1]:

    - hosts: web_servers
    
      tasks:
    
         - shell: /usr/bin/foo
           register: foo_result
           ignore_errors: True
    
         - shell: /usr/bin/bar
           when: foo_result.rc == 5

How would I save `foo_result` variable to a file e.g. `foo_result.log` using ansible?

  [1]: http://docs.ansible.com/playbooks_variables.html#registered-variables

All Ansible Playbook Solutions on Gang of Coders

Total of 38 Ansible Playbook Solutions