All of my playbooks are failing after upgrading ansible-core from 2.18.7-1 to 2.19.0-1. A simple playbook such as: --- - name: Show info on cisco devices hosts: <redacted> connection: network_cli gather_facts: false vars: ansible_network_os: ios ansible_user: <redacted> ansible…

Yep, that looks about right. Thanks for linking the github issue, dunno why I wasn’t able to find it earlier. I’ll be downgrading to 2.18.7 until ansible.netcommon catches up to 2.19.0. Thanks for the help.

@REDWINE welcome to the Ansible forum. I’ve let the Engineering team that looks after this collection know. Unsure why the GitHub issues hadn’t been looked at. I’ve changed the post title so it’s a little clearer

We are working on fixing the compatibility of ansible.netcommon with core-2.19 Would be sharing updates shortly.

A PR has been started, though it’s still work in progress WIP Fix facts for 2.19 failures main ← KB-perByte:fix_fr_219 opened 05:32AM - 24 Jul 25 UTC (UTC) …

Quick update: The recent enhancements in 2.19 broke the direct execution behavior of network content - specifically when ansible.netcommon patches _load_params during ActionModule calls, preventing argument loading from sys.argv. We’re actively working on a fix to restore the default behavior and …

Right now almost all of the network collections (arista.eos, junipernetwork.junos, cisco.ios, cisco.nxos) are broken with Ansible Core 2.19 which is part of Ansible Community 12. As of late July, 2025, Ansible Core 2.19 is currently released, and Ansible Community 12 will be released in a few days. …

Maybe it would be useful to add links to network collections in this thread with info on whether they are known to work (or not). Work on ansible.netcommon is kind of tracked here: Validate compatibility with ansible-core 2.19 · Issue #698 · ansible-collections/ansible.netcommon · GitHub Ansible 12…

Thanks for adding that link. The following network modules use netcommon, and there may be more. CloudEngine CNOS Dell OS6/9/10 ENOS Arista EOS ERIC_ECCLI EXOS FRR ICX Cisco IOS Cisco IOS XR Cisco NXOS Juniper Junos NETVISOR Extreme NOS Extreme VOSS RouterOS SLX-OS VyOS Westermo WeOS 4 (never hea…

[image] shadeland: I’m a little frustrated that 2.19 was released even though there was a known problem as far back as May with netcommon, a collection that a lot of other modules rely on. I agree that the current situation is really bad (and very frustrating), since a lot of collections appa…

Yeah, I know a few maintainers have been caught off guard, but isn’t netcommon maintained by Red Hat? I would have thought this would have been a bit more coordinated.

Ansible.netcommon broken with Ansible Core 2.19.0

Get Help

shertel July 23, 2025, 6:47pm 2

I believe this is because the ansible.netcommon collection is not compatible with 2.19. This error was also reported here: Validate compatibility with ansible-core 2.19 · Issue #698 · ansible-collections/ansible.netcommon · GitHub.

Topic		Replies	Views
Ansible 12.0.0 release schedule Project Discussions community-wg , release-management , ansible	36	635	September 5, 2025
Core-2.19 templating changes - preview and testing Project Discussions awx , fedora , ansible-core , ansible-lint , aap , templating	56	4608	June 21, 2025
Adjust Ansible 12 release schedule Project Discussions community-wg , release-management , ansible	31	693	September 2, 2025
Opening issues against all collections in Ansible for core-2.19 template testing Collection Development community-wg , templating	23	360	April 26, 2025
Problem upgrading to Ansible 2.19 Get Help azure , ee	18	384	January 26, 2026

Ansible.netcommon broken with Ansible Core 2.19.0

Related topics