Updating the ansible credentials to leave out the privelege escalation
worked thanks
On Tuesday, March 22, 2016 at 10:15:44 PM UTC+1, Brian Coca wrote:
>
> I believe the issue is you are using become wrong, as per that sudoers
> file you can just leave the `become_user: root` and it will work
If i go into visudo (centos) I have the following
sshUser ALL=(ALL) NOPASSWD: ALL
machineAdminALL=(ALL) NOPASSWD: ALL
so yes?
On Tuesday, March 22, 2016 at 9:48:25 PM UTC+1, Benjamin Redling wrote:
>
> On 2016-03-22 20:25, Aaron Axisa wrote:
> > TASK [gosa :
If i run the yum install as the machineAdmin user it is fine on the
machine. Ansible is somehow losing the privledges?
And it's using su machineAdmin cause ansible tower is configured that the
sshUser's privelege escalation is of type su and with credentials for
machineAdmin
(In reality both
TASK [gosa : Install EPEL Package]
* task path:
/var/lib/awx/projects/_8__bitbucket_ldap/ansible/roles/gosa/tasks/main.yml:15
<192.168.20.4>
ESTABLISH SSH CONNECTION FOR USER: sshUser <192.168.20.4> SSH: ansible.cfg
set ssh_args:
I have the following playbook
---
- name: myPlaybook
hosts: "{{machine_to_setup}}"
remote_user: "{{user_to_use}}"
become: yes
roles:
# Install Gosa - part 1
- { role: gosa, become: yes }
(I know become is duplicated.
With the following role content:
---
# Requires Ansible
I am trying to use yumrepo
https://docs.ansible.com/ansible/yumrepo_module.html
and it states that it is new in version 2.1
So i went ahead and updated ansible on my ansible tower machine:
sudo yum -y install git asciidoc rpm-build python2-devel
cd ~
git clone
