Content
Today I learned how to use Ansible conditionals (
when) to execute different tasks on different managed hosts within a single playbook. Instead of creating separate playbooks for each server, I used the built-inansible_nodenamefact to determine which task should run on each host.
๐น What I Learned
Using Ansible
whenconditionalsUnderstanding the
ansible_nodenamefactRunning a playbook against all hosts
Executing host-specific tasks within a single playbook
Using the Copy module to transfer files
Setting file ownership, group ownership, and permissions
๐น Task Requirement
An inventory file was already available under:
/home/thor/ansible/inventory
containing all three Stratos application servers.
I needed to create the following playbook:
/home/thor/ansible/playbook.yml
using Ansible when conditionals to perform different tasks depending on the target server.
The requirements were:
App Server 1
Copy:
/usr/src/finance/blog.txt
to
/opt/finance/blog.txt
with:
owner =
tonygroup =
tonypermissions =
0777
App Server 2
Copy:
/usr/src/finance/story.txt
to
/opt/finance/story.txt
with:
owner =
stevegroup =
stevepermissions =
0777
App Server 3
Copy:
/usr/src/finance/media.txt
to
/opt/finance/media.txt
with:
owner =
bannergroup =
bannerpermissions =
0777
The playbook also had to:
run against all hosts
use
ansible_nodenamewithwhenexecute successfully using:
ansible-playbook -i inventory playbook.yml
without passing any additional arguments.
๐น Steps I Followed
1. Navigated to the Ansible Working Directory
I first moved to the Ansible project directory.
cd ~/ansible
2. Verified the Available Files
I checked the contents of the directory.
ls
Output:
ansible.cfg
inventory
Observation
The inventory file was already present, so only the playbook needed to be created.
3. Examined the Inventory
Before writing the playbook, I verified the inventory configuration.
cat inventory
Output:
stapp01 ansible_host=stapp01 ansible_ssh_pass=Ir0nM@n ansible_user=tony
stapp02 ansible_host=stapp02 ansible_ssh_pass=Am3ric@ ansible_user=steve
stapp03 ansible_host=stapp03 ansible_ssh_pass=BigGr33n ansible_user=banner
Observation
The inventory already contained all three application servers.
Each host had its own SSH login user:
stapp01โtonystapp02โstevestapp03โbanner
The task, however, explicitly required assigning ownership to these users, so I specified the owner and group directly in each task.
4. Created the Playbook
I created the playbook.
vi playbook.yml
Added the following content:
---
- name: Copy finance files using when conditionals
hosts: all
become: yes
gather_facts: yes
tasks:
- name: Copy blog.txt to App Server 1
ansible.builtin.copy:
src: /usr/src/finance/blog.txt
dest: /opt/finance/blog.txt
owner: tony
group: tony
mode: '0777'
when: ansible_nodename == "stapp01"
- name: Copy story.txt to App Server 2
ansible.builtin.copy:
src: /usr/src/finance/story.txt
dest: /opt/finance/story.txt
owner: steve
group: steve
mode: '0777'
when: ansible_nodename == "stapp02"
- name: Copy media.txt to App Server 3
ansible.builtin.copy:
src: /usr/src/finance/media.txt
dest: /opt/finance/media.txt
owner: banner
group: banner
mode: '0777'
when: ansible_nodename == "stapp03"
Saved the file.
Understanding the Playbook
The playbook runs against:
hosts: all
This means every managed host participates in the play.
Instead of executing every task on every server, the when condition determines whether a task should run.
For example:
when: ansible_nodename == "stapp01"
ensures that the task executes only on App Server 1.
If the current host is stapp02 or stapp03, Ansible skips that task automatically.
Understanding ansible_nodename
ansible_nodename is a fact collected during the Gathering Facts stage.
For each server, its value becomes:
| Server | ansible_nodename |
|---|---|
| App Server 1 | stapp01 |
| App Server 2 | stapp02 |
| App Server 3 | stapp03 |
Using this variable allows a single playbook to perform different operations on different hosts.
Understanding the Copy Module
The Copy module transfers files from the Ansible control node to managed hosts.
For each task it:
copies the required file
creates the destination file
sets the owner
sets the group
applies the required permissions
For example:
ansible.builtin.copy:
copies:
/usr/src/finance/blog.txt
to
/opt/finance/blog.txt
and applies:
owner: tony
group: tony
mode: '0777'
during the copy operation.
5. Executed the Playbook
After saving the playbook, I executed it.
ansible-playbook -i inventory playbook.yml
Output:
PLAY [Copy finance files using when conditionals]
TASK [Gathering Facts]
ok: [stapp02]
ok: [stapp03]
ok: [stapp01]
TASK [Copy blog.txt to App Server 1]
skipping: [stapp02]
skipping: [stapp03]
changed: [stapp01]
TASK [Copy story.txt to App Server 2]
skipping: [stapp01]
skipping: [stapp03]
changed: [stapp02]
TASK [Copy media.txt to App Server 3]
skipping: [stapp01]
skipping: [stapp02]
changed: [stapp03]
PLAY RECAP
stapp01 : ok=2 changed=1 skipped=2
stapp02 : ok=2 changed=1 skipped=2
stapp03 : ok=2 changed=1 skipped=2
๐น Understanding the Output
Gathering Facts
Ansible first collected facts from every managed host.
These facts included ansible_nodename, which was later used by the when conditions.
Conditional Execution
Only the matching task executed on each server.
For example:
On stapp01:
changed: [stapp01]
while the other two tasks were skipped.
The same behavior occurred for the remaining servers.
This confirms that the when conditions worked correctly.
Play Recap
ok=2
changed=1
skipped=2
failed=0
for each server.
Observation
Each server executed exactly one copy task while skipping the other two.
No failures occurred during execution.
6. Verified the Configuration
App Server 1
ansible stapp01 -i inventory -m shell -a "ls -l /opt/finance/"
Output:
-rwxrwxrwx 1 tony tony 35 Jul 2 17:18 blog.txt
Observation
Verified:
Owner =
tonyGroup =
tonyPermissions =
0777
App Server 2
ansible stapp02 -i inventory -m shell -a "ls -l /opt/finance/"
Output:
-rwxrwxrwx 1 steve steve 27 Jul 2 17:18 story.txt
Observation
Verified:
Owner =
steveGroup =
stevePermissions =
0777
App Server 3
ansible stapp03 -i inventory -m shell -a "ls -l /opt/finance/"
Output:
-rwxrwxrwx 1 banner banner 22 Jul 2 17:18 media.txt
Observation
Verified:
Owner =
bannerGroup =
bannerPermissions =
0777
All three servers matched the task requirements.
๐น Verification
โ Created the required playbook
โ Executed the playbook on all hosts
โ
Used when conditionals
โ
Used ansible_nodename to identify each server
โ Copied the correct file to each application server
โ Set the correct owner and group
โ
Applied 0777 permissions
โ Successfully verified all copied files
๐น My Understanding
This task helped me understand how Ansible conditionals allow a single playbook to perform different actions on different hosts. By using ansible_nodename with the when statement, I could target specific tasks to individual servers while still running the playbook against all hosts. This approach keeps automation centralized, avoids duplicate playbooks, and makes managing host-specific operations much easier.
๐น What I Found Interesting
I found it interesting that a single playbook can handle multiple servers with completely different tasks simply by using when conditions. Instead of maintaining separate playbooks for each host, Ansible evaluates the condition for every managed node and automatically skips tasks that do not apply. This makes playbooks cleaner, more scalable, and easier to maintain as infrastructure grows.
๐ Full notes: GitHub link
- #using-ansible-conditionals
- #ansible
- #ansible-playbook
- #ansible-module
- #ansible-adhoc
- #ansible-automation
- #ansible-project
- #ansible-inventory-file
- #ansible-devops
- #ansible-conditionals
- #when
- #ansible-nodename
- #devops
- #devops-articles
- #devops-journey
- #devopscommunity
- #devops-trends
- #devops-tools
- #devops-engineer
- #devopsculture
- #devopsjourney
- #devopsproject
- #100daysofdevops
About the author
- Iโm currently working in DevOps and documenting my learning journey along the way. From CI/CD pipelines to cloud and containers, Iโm exploring how modern systems are built and deployed. This blog is where I share what I learn, break down concepts in simple terms, and track my progress. Learning one concept at a time, and trying to apply it practically.
Comments
Join the discussionNo comments yet. Be the first to comment.
100_days_of_devops
Documenting my 100 Days of DevOps journey with hands-on practice from KodeKloud, along with notes, commands, and mini projects