When Ansible misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- Non-idempotent shell/command tasks that run every time regardless of state
- Secrets in plaintext instead of Ansible Vault
- Giant single playbooks instead of reusable roles
Commands for diagnosis
ansible-playbook -i inventory.ini site.yml --check # dry run
ansible-playbook -i inventory.ini site.yml --diff
ansible-vault encrypt group_vars/prod/secrets.ymlPrevent the repeat
- Prefer modules over raw shell; add changed_when/creates to shell tasks
- Structure logic into roles and use group_vars/host_vars
- Encrypt secrets with Ansible Vault and keep the key out of the repo
Want senior help putting Ansible to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.