Hi,

What do you expect to happen (as in: should the yum task fail, wait, kill
the other yum process, ...)?

This is a safeguard from yum to keep you from shooting yourself in the
foot. I personally would simply let the yum module wait until completed and
if the task should be timeboxed use a wait_for before running the actual
yum task (http://docs.ansible.com/wait_for_module.html).

One approach may be to move the "auto updater" to ansible too (it could be
as simple as "yum: state=latest name=*"). That way you will have more
control when updates happen, the drawback is that you will need to find
another mechanism to run it regularly and if your control machine is down
then no host will be updated.

The basic problem is that you have two systems fighting over the control of
the system: the auto update and ansible. It's a classic race condition
where you just need to decide what is more important to you. Immediate runs
from ansible or updates applied to the hosts independently.

Another possibility would also be to use async:
http://docs.ansible.com/playbooks_async.html -- but that could also add a
lot of complexity.

/Martin

On Tue, Jun 23, 2015 at 10:56 AM Zohar Yu <[email protected]> wrote:

> I'm sorry for the late reply, I use the yum module and the shell module to
> install packages ,Sometimes i can encouter this problem .  when the remote
> host is updating,the remote host startup a yum process . at the same time,
> I use yum module of ansible to install some  packages,then the ansible wait
> there,no any feedback,
> in fact the problem is easy to reappear,example: in the remote host ,start
> a yum process and don't let it quit, then use yum module  or shell module
> of ansible to install some packages in the controller host ,then the same
> problem  will appear.
>
> --
> 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/7ecbf8b3-6405-4814-8a05-506c7d688698%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/7ecbf8b3-6405-4814-8a05-506c7d688698%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- 
http://www.xing.com/profile/Martin_Marcher
http://www.linkedin.com/in/martinmarcher
Mobil: +43 / 660 / 62 45 103
UID: ATU68801424

-- 
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/CAK1mKERJJLRai280tdD35u4rD1f8Me%3DbCay%2BfKOu0DWewELYFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to