Introduction Today we're going to talk about Ansible troubleshooting, specifically about missing sudo password and incorrect sudo password. I'm Luca Berton and welcome to today's episode of Ansible Pilot. Playbook The best way of talking about Ansible troubleshooting is to jump in a live Playbook to show you practically the missing sudo password and incorrect sudo password and how to solve it! error code - missingsudopassword_error.yml ```yaml --- - name: debug module Playbook hosts: all become: true tasks: - name: root test ansible.builtin.debug: msg: "privilege escalation successful" ``` error execution ```bash $ ansible-playbook -i Playbook/inventory troubleshooting/missingsudopassword_error.yml PLAY [debug module Playbook] ********************************************************************************* TASK [Gathering Facts] *********************************************************************************** fatal: [demo.example.com]: FAILED! => {"msg": "Missing sudo password"} PLAY RECAP *********************************************************************************************** demo.example.com : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 ``` troubleshoot ```bash $ ansible-playbook --help usage: ansible-playbook [-h] [--version] [-v] [-k] [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [...] Privilege Escalation Options: control how and which user you become as on target hosts --become-method BECOME_METHOD privilege escalation method to use (default=sudo), use `ansible-doc -t become -l` to list valid choices. --become-user BECOME_USER run operations as this user (default=root) -K, --ask-become-pass ask for privilege escalation password -b, --become run operations with become (does not imply password prompting) ansible-pilot $ ansible-playbook -i Playbook/inventory troubleshooting/missingsudopassword_error.yml -bK BECOME password: PLAY [debug module Playbook] ********************************************************************************* TASK [Gathering Facts] *********************************************************************************** fatal: [demo.example.com]: FAILED! => {"msg": "Incorrect sudo password"} PLAY RECAP *********************************************************************************************** demo.example.com : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 ``` verification ```bash $ ssh devops@demo.example.com Last login: Mon Nov 8 10:24:10 2021 from 192.168.43.5 [devops@demo ~]$ sudo su We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for devops: Sorry, try again. [sudo] password for devops: Sorry, try again. [sudo] password for devops: sudo: