Playbook fails with "Timeout (32s) waiting for privilege escalation prompt" in OCP 3

Solution Verified - Updated -


  • ansible playbook sometimes failed to run due to following errors. How to solve it?

<> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=cloud-user -o ConnectTimeout=10 -o ControlPath=/home/cloud-user/.ansible/cp/ansible-ssh-%h-%p-%r -tt '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-ukszyjhuvehniabbjycgqnwkcvvlrhpa; /usr/bin/python /home/cloud-user/.ansible/tmp/ansible-tmp-1481685198.89-220235001309076/; rm -rf "/home/cloud-user/.ansible/tmp/ansible-tmp-1481685198.89-220235001309076/" > /dev/null 2>&1'"'"'"'"'"'"'"'"' && sleep 0'"'"''
fatal: []: FAILED! => {
    "failed": true,
    "msg": "Timeout (12s) waiting for privilege escalation prompt: "

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
localhost                  : ok=10   changed=9    unreachable=0    failed=0 : ok=56   changed=4    unreachable=0    failed=0 : ok=54   changed=3    unreachable=0    failed=1


  • Red Hat OpenShift Container Platform (OCP)
    • 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In