On Thursday, May 8, 2014 1:56:35 PM UTC-7, Anand Buddhdev wrote: > > On Thursday, 8 May 2014 22:50:26 UTC+2, Adam Morris wrote: > > Actually, this looks like a bug that occurred with script and raw in some >> earlier versions of Ansible where the sudo success string was being leaked >> back. It was fixed, I'm now wondering if it was reverted in this case... >> >> Can you upgrade to 1.6.1 and try it again? >> > > Hi Adam, it still fails: > > $ ansible --version > ansible 1.6.1 > $ ansible bastion3.hadoop.ripe.net -sK -m service -a 'name=hdfs-sync > state=restarted' > sudo password: > bastion3.hadoop.ripe.net | FAILED => failed to parse: > SUDO-SUCCESS-dawyrikofupcjoyftolafyddywphopwj > There is an open bug report https://github.com/ansible/ansible/issues/7319 which sounds very similar...
Do you need to provide a password to use sudo on the remote host? Do you need to use sudo? I'm curious because that first line SUDO-SUCCESS ... should be being eaten by part of ansible... Adam -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f83209ee-d187-4816-91dc-3668d250d27c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
