Ansible.netcommon broken with Ansible Core 2.19.0

Get Help
, ,
1

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_password: !vault | <redacted>
    ansible_connect_timeout: 10

  tasks:
    - name: show me something
      ios_command:
        commands:
          - show run | i hostname
      register: output

    - debug:
        msg: "{{ output.stdout_lines }}"

Fails with the following error:

PLAY [Show info on cisco devices] ***********************************************************************************************************

TASK [show me something] ********************************************************************************************************************
[WARNING]: Deprecation warnings can be disabled by setting `deprecation_warnings=False` in ansible.cfg.
[DEPRECATION WARNING]: Passing `warnings` to `exit_json` or `fail_json` is deprecated. This feature will be removed from ansible-core version 2.23. Use `AnsibleModule.warn` instead.
[ERROR]: Task failed: ActionBase._parse_returned_data() missing 1 required positional argument: 'profile'
Origin: <redacted>.yaml:19:7

17
18   tasks:
19     - name: show me something
         ^ column 7

fatal: [<redacted>]: FAILED! => {"changed": false, "msg": "Task failed: ActionBase._parse_returned_data() missing 1 required positional argument: 'profile'"}

PLAY RECAP **********************************************************************************************************************************
<redacted>           : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Downgrading the ansible-core package back to 2.18.7-1 allows this playbook to run successfully. Anybody seeing similar issues or has any insight into this error? Hereā€™s my environment:

ansible [core 2.19.0]
  python version = 3.13.5 (main, Jun 21 2025, 09:35:00) [GCC 15.1.1 20250425] (/usr/bin/python)
  jinja version = 3.1.6
  pyyaml version = 6.0.2 (with libyaml v0.2.5)

Issue is reproduceable across multiple PCs running Arch Linux.

1 Like
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.

5 Likes
3

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.

4

@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

5

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

2 Likes
6

A PR has been started, though itā€™s still work in progress

1 Like