# Quick ping on a bug

**URL:** <https://forum.ansible.com/t/quick-ping-on-a-bug/19400>\
**Category:** Ansible Project\
**Created:** [October 1, 2015, 8:36am UTC](https://forum.ansible.com/t/quick-ping-on-a-bug/19400 "2015-10-01T08:36:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jang](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@jang](https://forum.ansible.com/u/jang)\
**Post date:** [October 1, 2015, 8:36am UTC](https://forum.ansible.com/t/quick-ping-on-a-bug/19400/1 "2015-10-01T08:36:20Z")

</div>

This got a P2, bug-report about three weeks ago:

&nbsp;&nbsp;[https://github.com/ansible/ansible/issues/12305](https://github.com/ansible/ansible/issues/12305)

but the moved version is languishing:

&nbsp;&nbsp;[https://github.com/ansible/ansible-modules-core/issues/2051](https://github.com/ansible/ansible-modules-core/issues/2051)

The fix is inline in the bug. Any chance of pushing this?

Cheers,  
jan

---

<div class="post-metadata">

**Author:** ![Greg\_DeKoenigsberg1](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Greg\_DeKoenigsberg1](https://forum.ansible.com/u/Greg_DeKoenigsberg1)\
**Post date:** [October 1, 2015, 2:29pm UTC](https://forum.ansible.com/t/quick-ping-on-a-bug/19400/2 "2015-10-01T14:29:18Z")

</div>

Jan, thanks for filing the bug. The surest way of getting attention on  
this kind of issue, especially if the code is in the issue, is to  
simply file a PR.

We'll go ahead and notify the module owners of the issue.

--g