# Ansible.netcommon broken with Ansible Core 2.19.0

**URL:** <https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043>\
**Category:** Get Help\
**Tags:** cisco, templating, network\
**Created:** [July 23, 2025, 6:46pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043 "2025-07-23T18:46:00Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\
**Post date:** [August 1, 2025, 4:26pm UTC](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/18 "2025-08-01T16:26:24Z")

</div>

> <https://github.com/ansible/ansible/pull/85609>
>
> \##### SUMMARY
> Temporary hook to allow \`ansible.netcommon\` to entirely monkeypat…ch away module result serialization until direct module execution in core workers is actually supported.
> 
> \##### ISSUE TYPE
> \- Feature Pull Request

> <https://github.com/ansible-collections/ansible.netcommon/pull/711>
>
> \##### SUMMARY
> \* Overrides new 2.19.1+ AnsibleModule.\_record\_module\_result hook …in base network action plugin to entirely bypass module result serialization on 2.19.1+ when direct execution is enabled.
> 
> \##### ISSUE TYPE
> \- Bugfix Pull Request
> 
> \##### COMPONENT NAME
> plugins/action/network.py
> 
> \`\`\`

Credits @nitzmahone

Sharing some in-progress PRs that are targeted to address the problems at hand.  
This does not require the workaround suggested previously. And fixes the direct execution behaviour of network modules.  
The above-mentioned PRs are being tested. More updates regarding that will be shared.

Regards.

---

_[View the full topic](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043)._