Fix Ansible Privilege Escalation: sudo Config

If you are seeing privilege escalation failed when running Ansible, here is how to fix it.

What This Error Means

sudo or su failed on the remote host. User not in sudoers, wrong password, or requiretty set.

Quick Diagnosis

# Run with verbose output
ansible-playbook playbook.yml -vvv

# Syntax check first
ansible-playbook playbook.yml --syntax-check

# Check in dry-run mode
ansible-playbook playbook.yml --check --diff

How to Fix It

Step 1: Identify the Root Cause

The -vvv output will show you exactly where the error occurs and what went wrong.

Step 2: Apply the Fix

sudo or su failed on the remote host. User not in sudoers, wrong password, or requiretty set.

Review your playbook, inventory, and variable files. Test with --check before applying.

Step 3: Verify

# Run again and confirm no errors
ansible-playbook playbook.yml

# Should complete with 0 failures

Prevention Tips

• Always use --syntax-check before running playbooks
• Use ansible-lint to catch common mistakes
• Test with Molecule before deploying to production
• Use FQCNs (Fully Qualified Collection Names) for all modules
• Keep Ansible and collections updated

Related Resources

• Ansible Playbook Examples
• Ansible Tutorial for Beginners
• Terraform vs Ansible
• RHCE Exam Prep