# ansible executing every other task

**URL:** <https://forum.ansible.com/t/ansible-executing-every-other-task/19704>\
**Category:** Ansible Project\
**Created:** [November 6, 2015, 6:11pm UTC](https://forum.ansible.com/t/ansible-executing-every-other-task/19704 "2015-11-06T18:11:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jon1](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@Jon1](https://forum.ansible.com/u/Jon1)\
**Post date:** [November 6, 2015, 6:11pm UTC](https://forum.ansible.com/t/ansible-executing-every-other-task/19704/1 "2015-11-06T18:11:31Z")

</div>

I’m running:  
ansible 2.0.0 (devel [`5b84bd6`](https://github.com/ansible/ansible/commit/5b84bd6b5d2bcf9aa835303610a44c729e3657d7)) last updated 2015/11/06 08:18:12 (GMT -500)  
lib/ansible/modules/core: (detached HEAD 35707bcb3c) last updated 2015/11/06 08:18:15 (GMT -500)  
lib/ansible/modules/extras: (detached HEAD f281eb2b30) last updated 2015/11/06 08:18:17 (GMT -500)

when I execute tasks, it appears to be skipping every other task.  
I get the following output:

TASK [baseserver-role : apt state=installed pkg=lynx] \*\*\*

TASK [baseserver-role : apt state=installed pkg=links] \*\*\*  
changed: [10.0.0.27]

TASK [baseserver-role : apt state=installed pkg=elinks] \*\*\*

TASK [baseserver-role : apt state=installed pkg=curl] \*\*\*  
changed: [10.0.0.27]

TASK [baseserver-role : apt state=installed pkg=wget] \*\*\*

TASK [baseserver-role : apt state=installed pkg=mysql-client] \*\*\*  
ok: [10.0.0.27]

and when I go to the server, only every other package has been installed.

Anyone have any idea why this would be happening?

Thanks,

Jon.

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [November 9, 2015, 3:15pm UTC](https://forum.ansible.com/t/ansible-executing-every-other-task/19704/2 "2015-11-09T15:15:20Z")

</div>

Just to follow-up on this, we had already found and resolved this bug, which was caused by a small change in the way workers were created to handle tasks. If anyone still sees this, they should simply update to the latest checkout of devel.