Hi Frederick/Dylan
I have the same problem. The repo query is being made to every single build
of a package, thus making the yum install several mins.
I did set the keepcache to 1 in /etc/yum.conf. but that did not fix the
issue. Could you share what those settings exactly are?
Thanks
Bala
I realize that this will probably qualify for non-Ansible way, but here's
how I had to resolve similar issue:
1. split playbook into "install" and "setup" whereas install is ran only
once in a while if you need to change list of packages installed etc. -
resolves issues with RHN etc. setup can
Ok, thanks for info.
Probably something that should be addressed on yum's end as we do need the
latest information to decide whether to run certain commands or not.
While it is possible to just run the command and report back what it
changed (or didn't), that's not Ansible's way when it can avoid
>
> We set up a local RHEL mirror just this week, thinking that that would
> speed up ansible. It didn't.
>
> Running "yum: state=latest" entails running repoquery numerous times for
> each package involved, based on snooping with "ps". A typical such
> repoquery takes about two seconds on my m
If you are seeing long times with state=latest, I'd suspect you maybe have
RHN to blame. I always recommend a local mirror if so. If you aren't
having RHN involved, perhaps you are still using a slow mirror.
--
You received this message because you are subscribed to the Google Groups
"Ansible
Thank you, Alex! This works great for me in RHEL 6.5. It had been taking
several minutes to run "yum state=latest" for just four packages (already
installed). Now it finishes in just a few seconds.
I was getting close to giving up on ansible because of the huge delays in
every "yum" step. All
