Ansible - "Destination /etc/yum.repos.d not writable"

Ron_1984

New Member
Credits
172
Yes, the playbook for yum update is working fine on the new RHEL systems, but i get hung on the TASK [sudo update] in our old systems. I could not find if there is any local customization is done for the yum configurations on the old systems.

Any suggestions on what are the files I need to check on the old systems?

Playbook
tasks:
- name: sudo update
yum:
name: '*'
state: latest
 


f33dm3bits

Gold Member
Gold Supporter
Credits
12,808
I have no way to know what changes you have made to your systems, it seems to be working fine on my Rhel7 test system. Are you able to do a yum update manually or yum repolist on the old system without running into a problem? What error do you get if you wait when it hangs until ansible gives up?

What I would do is install a clean Rhel7 system without anything extra, give full sudo access rights to the the remote_user for ansible and then try to run your playbook. See if that runs correctly if it does, add one of the sudo changes you have on your old systems, do another run and do that until you come across the setting that makes ansible hang on your old systems.
 

Ron_1984

New Member
Credits
172
Hi
I lcoated the local customization for yum configuration. it was residing on /usr/local/bin/yum.. this script made the ansible playbook for yum update to hung.
Playbook ran fine after I have removed the script. Thank you
 

Members online


Top