Ansible 2.0: Timeout (0s) waiting for privilege escalation prompt

Archives Ansible Developer
1

Hey gang,

I’ve been using Ansible 2.0 since it contains lots of new winrm features I’m heavily leveraging, but it looks like it’s breaking on my Linux hosts. I’ve been getting this at various points in several playbooks:

`
<rundeck.atxd.maxpointinteractive.com> ESTABLISH SSH CONNECTION FOR USER: maxpoint
<rundeck.atxd.maxpointinteractive.com> SSH: EXEC sshpass -d14 ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o User=maxpoint -o ConnectTimeout=10 -o ControlPath=/tmp/ansible-ssh-%h-%p-%r -tt rundeck.atxd.maxpointinteractive.com (umask 22 && mkdir -p “$(echo /tmp/ansible-tmp-1445025552.51-664872202787)” && echo “$(echo /tmp/ansible-tmp-1445025552.51-664872202787)”)
<rundeck.atxd.maxpointinteractive.com> ESTABLISH SSH CONNECTION FOR USER: maxpoint
<rundeck.atxd.maxpointinteractive.com> SSH: EXEC sshpass -d14 ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o User=maxpoint -o ConnectTimeout=10 -o ControlPath=/tmp/ansible-ssh-%h-%p-%r -tt rundeck.atxd.maxpointinteractive.com /bin/sh -c ‘sudo -H -p “[sudo via ansible, key=gyxnrmzoffwalwbfwndwcyeppauahhzm] password: " -S -u root /bin/sh -c '”’“'echo BECOME-SUCCESS-gyxnrmzoffwalwbfwndwcyeppauahhzm; rc=flag; [ -r /tmp/restcs_release-1.0.7 ] || rc=2; [ -f /tmp/restcs_release-1.0.7 ] || rc=1; [ -d /tmp/restcs_release-1.0.7 ] && rc=3; python -V 2>/dev/null || rc=4; [ x”$rc" != “xflag” ] && echo “${rc} “/tmp/restcs_release-1.0.7 && exit 0; (python -c '”'”‘"’“'”‘"’“'”‘import hashlib; BLOCKSIZE = 65536; hasher = hashlib.sha1();
afile = open("’“'”‘"’“'”‘"’“'”‘/tmp/restcs_release-1.0.7’“'”‘"’“'”‘"’“'”‘", “rb”)
buf = afile.read(BLOCKSIZE)
while len(buf) > 0:
hasher.update(buf)
buf = afile.read(BLOCKSIZE)
afile.close()
print(hasher.hexdigest())’“'”‘"’“'”‘"’“'”’ 2>/dev/null) || (python -c ‘"’“'”‘"’“'”‘"’“'import sha; BLOCKSIZE = 65536; hasher = sha.sha();
afile = open(”‘"’“'”‘"’“'”‘"’“‘/tmp/restcs_release-1.0.7’”‘"’“'”‘"’“'”‘"’“, “rb”)
buf = afile.read(BLOCKSIZE)
while len(buf) > 0:
hasher.update(buf)
buf = afile.read(BLOCKSIZE)
afile.close()
print(hasher.hexdigest())'”‘"’“'”‘"’“'”‘"’ 2>/dev/null) || (echo ‘"’“'”‘"’“'”‘"’“'0 '”‘"’“'”‘"’“'”‘"’/tmp/restcs_release-1.0.7)‘"’"‘’
<rundeck.atxd.maxpointinteractive.com> ESTABLISH SSH CONNECTION FOR USER: maxpoint
<rundeck.atxd.maxpointinteractive.com> SSH: EXEC sshpass -d14 ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o User=maxpoint -o ConnectTimeout=10 -o ControlPath=/tmp/ansible-ssh-%h-%p-%r -tt rundeck.atxd.maxpointinteractive.com (umask 22 && mkdir -p “$(echo /tmp/ansible-tmp-1445025553.69-65442728925021)” && echo “$(echo /tmp/ansible-tmp-1445025553.69-65442728925021)”)
fatal: [rundeck.atxd.maxpointinteractive.com]: FAILED! => {“failed”: true, “msg”: “ERROR! Timeout (0s) waiting for privilege escalation prompt: /tmp/ansible-tmp-1445025553.69-65442728925021\r\n”}

`

I’ve tried pulling down latest and using that – Same problem. I am proxying through a jumphost, and someone on the old git issue suggested that was the problem, and that he issue seemed tied to running with “sudo: yes”. I found that if I used “become: yes” it would sometimes get past this point, but then die on a call to “synchronize” that gets delegated to the remote machine (I was going to make a new post about that issue).

https://github.com/ansible/ansible/issues/11808

But thought I should post here since it gets a little more visibility.

Any thoughts?

2

Also worth noting that I was originally running the v2 beta, but then pulled down devel and the problem persisted.