Resolved by changing *su* to *sudo* in *become_method*, i.e. changing
become_method:su to become_method: su*do**. *The docs mention *su* however.
Is this a bug in Ansible itself where it say in the error message that *su*
is not acceptable or are *su* and *sudo* meant to do different things?
On Saturday, August 8, 2020 at 2:23:09 AM UTC+5:30 lovesh harchandani wrote:
> Hi.
> I am trying to install a package on an AWS Ubuntu machine using ansible
> and getting error
>
> FAILED! => {"msg": "Timeout (42s) waiting for privilege escalation prompt:
> "}
>
> I have tried with high timeouts as suggested online. The package I am
> trying to install is docker and so it should take much time.
> Moreover, I am watching the file /var/log/auth.log while I run the
> playbook but cannot see any activity.
> *I am able to do non-sudo actions however.*
>
> My ansible playbook is as follows
>
> - hosts: '{{ host }}'
> tasks:
> - name: run lsb_releaset to check SSH works
> shell: lsb_release -a
> - name: Install docker if not already
> become: yes
> become_method: su
> package:
> name: "docker-ce"
> state: present
>
> And my hosts file is as
>
> [node]
> <IP of the machine>
>
> [node:vars]
> ansible_ssh_user=ubuntu
> ansible_ssh_private_key_file=<my pem file location>
>
> I am running ansible as
>
> ansible-playbook -i hosts playbook.yml --extra-vars "host=node" -T 40 -v
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/1c6fde35-f469-4da6-9d84-bf44db250194n%40googlegroups.com.
