Hello, When I run a command that asks for user input, Ansible 1.4.4 hangs without any indication of what is going on. When I interrupt it with Ctrl-C, it prints a stacktrace that also contains noindication of the root cause.
I have been running "*command: /usr/bin/unzip /my-archive.zip*". I was only able to discover the problem - unzip asking whether it should overwrite an existing file - after killing the unzip command, at which point Ansible printed its stderr that contained the prompt from unzip. This was quite hard to detect, is there something that Ansible could do to help users troubleshoot such cases? I guess that it even a simple thing could be of a great help, such as having an interrupt handler in the command module and, upon interrupt, printing something like: "It looks like you have killed this command. If it seemed to have hanged, check that it wasn't asking for user input. You may also want to set command execution timeout by doing .... and running Ansible with -vvvv to troubleshoot it. Always make sure the command is non-interactive, f.ex. by setting appropriate command line options, if it has them." If it could actually also print stderr and perhaps (tail of?) stdout of the command, it would be terrific. Thank you! Best regards, Jakub Holy, Puppet renegade and Ansible newbie -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
