# ansible didn't stop execution upon a task failure

**URL:** <https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893>\
**Category:** Ansible Project\
**Created:** [November 30, 2015, 8:11am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893 "2015-11-30T08:11:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Leon\_Xie](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Leon\_Xie](https://forum.ansible.com/u/Leon_Xie)\
**Post date:** [November 30, 2015, 8:11am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/1 "2015-11-30T08:11:11Z")

</div>

hi

I have the below ansible playbook named backup\_data.yml, which is included by the main playbook named upgrade.yml.

backup\_data.yml

---

<div class="post-metadata">

**Author:** ![Leon\_Xie](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Leon\_Xie](https://forum.ansible.com/u/Leon_Xie)\
**Post date:** [November 30, 2015, 8:17am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/2 "2015-11-30T08:17:00Z")

</div>

ansible version is as below:

#ansible --version  
[WARNING]: The version of gmp you have installed has a known issue regarding  
timing vulnerabilities when used with pycrypto. If possible, you should update  
it (i.e. yum update gmp).

ansible 1.9.0.1  
configured module search path = None

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [November 30, 2015, 11:01pm UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/3 "2015-11-30T23:01:57Z")

</div>

only host 192.168.0.41 failed the task, hosts .42 and .43 continue the  
play, the play would abort if all hosts failed.

---

<div class="post-metadata">

**Author:** ![Leon\_Xie](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Leon\_Xie](https://forum.ansible.com/u/Leon_Xie)\
**Post date:** [December 1, 2015, 1:47am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/4 "2015-12-01T01:47:06Z")

</div>

Hi Brian,

Is there any way to abort 42 and 43 host if any task fails on 41 host?  
As I know, “any\_errors\_fatal: True” and " max\_fail\_percentage: 0’ can be used to archive this, however, it didn’t work.

thank

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [December 1, 2015, 2:22am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/5 "2015-12-01T02:22:34Z")

</div>

I don’t know, those options work for me.

---

<div class="post-metadata">

**Author:** ![Leon\_Xie](https://avatars.discourse-cdn.com/v4/letter/l/5e9695/32.png) [@Leon\_Xie](https://forum.ansible.com/u/Leon_Xie)\
**Post date:** [December 3, 2015, 8:04am UTC](https://forum.ansible.com/t/ansible-didnt-stop-execution-upon-a-task-failure/19893/6 "2015-12-03T08:04:42Z")

</div>

thanks a lot for your reply.