Andrey Chernih 7548024720 More verbose error message when ansible-playbook fails ... I've spent 1 hour today debugging why packer does not want to work with ansible. It turns out `ansible-playbook` command was returning non-zero exit status because of the file system permission problem. Output before change: % packer build rabbitmq.json amazon-ebs output will be in this color. 1 error(s) occurred: * exit status 1 Output after change: amazon-ebs output will be in this color. 1 error(s) occurred: * Error running "ansible-playbook --version": exit status 1		2017-03-21 20:26:41 -07:00
..
exit1	More verbose error message when ansible-playbook fails	2017-03-21 20:26:41 -07:00
long-debug-message.yml	Adding a functional test with an Ansible message very long	2016-07-07 01:12:57 +01:00