Kai: Thanks for the response but the issue with that solution is this is all dynamic and automated so there would be no person to respond. I have had to do some ENV things in order for each of the processes that need it to see the *.pem file generated at the beginning of the Ansible process that builds the AWS environment.
--- Perry Hoekstra On Friday, May 20, 2016 at 11:08:14 AM UTC-5, Kai Stian Olstad wrote: > > On 19. mai 2016 19:46, Perry Hoekstra wrote: > > The 'ec2_apache' role allocates an ec2 instance and the first task > within > > the apache/main.yml looks like this: > > > > - name: confirm using the latest Apache server > > become: yes > > become_method: sudo > > yum: > > name: httpd > > state: latest > > > > This is where the error message "sudo: a password is required" is > returned > > which leads me to believe I have somehow horked up with security. When > it > > fails, I can SSH into that newly created EC2 instance and do a 'sudo ls > > /etc" command. > > > > Thoughts on what I am doing wrong? > > You need to add the option --ask-become-pass to ansible-playbook or set > ask_become_pass = true in ansible.cfg or the inventory. > > -- > Kai Stian Olstad > -- 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/d5d57ca3-0263-4612-a2e6-bcc52f45d9fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
