# ansible 1.9.3 and the notification bug

**URL:** <https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401>\
**Category:** Ansible Project\
**Created:** [October 1, 2015, 9:08am UTC](https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401 "2015-10-01T09:08:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dalma](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dalma](https://forum.ansible.com/u/dalma)\
**Post date:** [October 1, 2015, 9:08am UTC](https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401/1 "2015-10-01T09:08:35Z")

</div>

Hi,

The same issue still exists as described in: [https://github.com/ansible/ansible/issues/11574](https://github.com/ansible/ansible/issues/11574)

Ansible is installed via pip.  
Is there a patch for this, where the playbook defined in the last comment works? It’s essential for us.

Thanks,  
Dalma Debreceni

---

<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:** [October 1, 2015, 2:00pm UTC](https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401/2 "2015-10-01T14:00:06Z")

</div>

the fix is in current devel, not in 1.9.3

---

<div class="post-metadata">

**Author:** ![dalma](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dalma](https://forum.ansible.com/u/dalma)\
**Post date:** [October 1, 2015, 2:13pm UTC](https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401/3 "2015-10-01T14:13:47Z")

</div>

so there’s no way we can use the stable version of 1.9?

---

<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:** [October 1, 2015, 2:19pm UTC](https://forum.ansible.com/t/ansible-1-9-3-and-the-notification-bug/19401/4 "2015-10-01T14:19:44Z")

</div>

not with that specific fix, the code is very different as the core was  
mostly rewritten. It would have to be a different fix, specifically  
for 1.9