ummm define properly :) Good question though. Installing ansible on an amazon ec2 instance is a pain in itself. So for the ec2-user, i can call out ansible with out any issues. I did have to jump through loops to get it installed. I'm thinking that whatever user packer runs as isn't able to find ansible. I want to figure out which user that is and then somehow export PATH for that user to make this successful.
When you say this worked for you, you have an ec2 machine with jenkins, packer and ansible installed and using jenkins job it was able to run with out failing? it may not be fruitful but I i'm going to try running packer directly to observe the result. Thanks for responding, hope you have some more inputs for me. On Thursday, September 28, 2017 at 2:53:59 PM UTC-4, Megan Marsh wrote: > > This works for me... do you have ansible installed properly on the machine > that's running packer? > > On Thu, Sep 28, 2017 at 10:38 AM, Gaurav Rastogi <grast...@gmail.com > <javascript:>> wrote: > >> Hi, >> >> I'm running an ec2 instance on aws. On this instance, I have jenkins, >> ansible and packer. I've created a jenkins job which uses the packer plugin >> and runs the packer.json file locally. When I run the job it fails with >> below output from jenkins console: >> >> Started by user admin <http://18.221.183.50/user/admin> >> Building in workspace /var/lib/jenkins/workspace/packer >> [packer] $ /usr/local/packer/packer build -debug >> /var/lib/jenkins/workspace/getrepopacker/packer.json >> Debug mode enabled. Builds will not be parallelized. >> [1;32mamazon-ebs output will be in this color. [0m >> >> 1 error(s) occurred: >> >> * Error running "ansible-playbook --version": exec: "ansible-playbook": >> executable file not found in $PATH >> Finished: FAILURE >> Build step 'Packer' marked build as failure >> Finished: FAILURE >> >> >> >> Any clues on how to solve this? >> >> >> Thanks >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/packer/issues >> IRC: #packer-tool on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Packer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to packer-tool...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/ea29fc9e-71f0-4840-a1c2-88796f04af61%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/ea29fc9e-71f0-4840-a1c2-88796f04af61%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- Confidentiality Note: This e-mail and any attachments are confidential and may be protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please notify us immediately by returning it to the sender and delete this copy from your system. Thank you for your cooperation. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/0896f392-8e4b-4ac7-85ac-95c2c25b8b9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
