@phy1729 can you please point out the exact lines in the second output which contain the problem.

I'd had redirected the output but not stderr so I could see the sudo prompt. Here's just a copy paste from the terminal https://gist.github.com/phy1729/8739115 The first warning is at line 34.

@phy1729 please "vagrant ssh" to the host, "sudo su -" and then run these two commands:

[ -r "/etc/dhcpd.conf" ] || rc=2; [ -f "/etc/dhcpd.conf" ] || rc=1; [ -d "/etc/dhcpd.conf" ] && rc=3; (/usr/bin/md5sum /etc/dhcpd.conf 2>/dev/null) || (/sbin/md5sum -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/digest -a md5 /etc/dhcpd.conf 2>/dev/null) || (/sbin/md5 -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/md5 -n /etc/dhcpd.conf 2>/dev/null) || (/bin/md5 -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/csum -h MD5 /etc/dhcpd.conf 2>/dev/null) || (echo "${rc}  /etc/dhcpd.conf")

echo $?

I would like to see the full output.

It's a actual server not a vagrant box.

$ sudo su -
A student asked the master for help... does this program run from the
Workbench? The master grabbed the mouse and pointed to an icon. "What is
this?" he asked. The student replied "That's the mouse". The master pressed
control-Amiga-Amiga and hit the student on the head with the Amiga ROM Kernel
Manual.
-- Amiga Zen Master Peter da Silva
20:03 root@lugbox ~>[ -r "/etc/dhcpd.conf" ] || rc=2; [ -f "/etc/dhcpd.conf" ] || rc=1; [ -d "/etc/dhcpd.conf" ] && rc=3; (/usr/bin/md5sum /etc/dhcpd.conf 2>/dev/null) || (/sbin/md5sum -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/digest -a md5 /etc/dhcpd.conf 2>/dev/null) || (/sbin/md5 -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/md5 -n /etc/dhcpd.conf 2>/dev/null) || (/bin/md5 -q /etc/dhcpd.conf 2>/dev/null) || (/usr/bin/csum -h MD5 /etc/dhcpd.conf 2>/dev/null) || (echo "${rc}  /etc/dhcpd.conf")
848eddf973dcff029db1160b2f3ba03d  /etc/dhcpd.conf
20:03 root@lugbox ~>echo $?
0

The quote changes each time.

@phy1729 so the md5sum is different? Can you run it a few times and show me the variations?

The hash is always the same. The quote after the sudo command changes.

I also realized that sudo is setup to be passwordless.

@phy1729 what connection mode are you using? (ssh/paramiko/smart)

What OS/version is the control machine?

What version of openssh is on the control machine?

ssh
OSX 10.7.5
OpenSSH_5.6p1, OpenSSL 0.9.8y 5 Feb 2013

I've got the same issue, I'm using a paramiko connection to a ScientificLinux 6.4 server from Ubuntu 13.10

I think I've found the bug. When ansible is called with --ask-sudo-pass, it runs on the remote like this:

sudo -k && sudo -H -S -p "[sudo via ansible, key=SOME_HASH_CANARY] password: " -u root /bin/sh -c "echo SUDO-SUCCESS_SOME_OTHER_CANARY; /usr/bin/python [...]"

Now, when sudo is configured to run passwordless, but ansible runs with --ask-sudo-pass, it expects sudo to ask for a password and expects sudo to actually show that prompt. sudo doens't do that, the output isn't what ansible expects, hence the warning

So as far as I can tell, this is not an error, but instead is happening because the SSH connection to the host is failing. The _remote_md5() function doesn't check the return code from the execution of the SSH connection to run the md5sum commands, and just tries to parse the data that is returned (which is an empty string because of the error). Oddly, in the original output, the rc=0 (when I reproduced this, it was 255).

Probably the best solution would be to detect an empty stdout from the execution of the md5sum commands and return "INVALIDMD5SUM" in that case. I think this is the course I'm going to take for now.

This should now be resolved in the devel branch. Please let me know if you continue to have problems with this issue. Thanks!