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.
Most of the issues can be traced to netcommon, which most of them use for various functions. But at least a few (such as arista.avd) are broken in other ways as well.
The most common ways of installing Ansible for network admins are “pip3 install ansible” or “pip3 install ansible-core”, which will install the broken versions (pip3 install ansible installs 11 now, but will install 12 by default in a few days).
You can install Ansible 11/Core 2.18 by doing “pip3 install ansible~=11” or “pip3 install ansible-core~=2.18” to get the most recent minor release of 11/2.18, respectively.
I know there’s a fix in for netcommon and that should resolve some of the issues, perhaps all for your use case. But it might be a while before Ansible 12/Core 2.19 is suitable for the networking world.
Edit: Added error messages so network admins can find this post in searches:
Here are the error messages you’d see with most networking modules using netcommond:
Task failed: ActionBase._parse_returned_data() missing 1 required positional argument: 'profile'