No module named 'ansible.module_utils.common.sentinel'

[LeFouineur]

Hi,

I just installed the aoscx ansible collection and when I try to test my installation, I get the following error

error

[...]
from ansible.module_utils.common.sentinel import Sentinel  # pylint: disable=unused-import\n    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nModuleNotFoundError: No module named 'ansible.module_utils.common.sentinel'\n",
    "module_stdout": "",
    "msg": "Module result deserialization failed: No start of json char found",
    "rc": 1
}

Is it linked to the new version of Ansible ? My configuration ? Or a bug ?

Here are the inventory and playbook used :

inventory/switch-test.yml

all:
  hosts:
     switch-test:
      ansible_host: switch-test.domain.local
      ansible_user: ansible
      ansible_password: ansible
      ansible_network_os: arubanetworks.aoscx.aoscx
      ansible_connection: arubanetworks.aoscx.aoscx
      ansible_httpapi_validate_certs: False
      ansible_httpapi_use_ssl: True
      ansible_acx_no_proxy: True
      ansible_aoscx_validate_certs: False
      ansible_aoscx_use_proxy: False

playbook/test.yml

- hosts: switch-test
  collections:
    - arubanetworks.aoscx
  gather_facts: False
  tasks:
    - name: Create VLAN 550 with description and name
      aoscx_vlan:
        vlan_id: 550
        name: test_VLAN
        description: This is VLAN 550

Switches

Model : CX6100

Configuration Server

OS

Ubuntun 25.10 (CLI)

Env

Using a virtual python env (/home/user/ansible/.venv)

Ansible Configuration

ansible [core 2.20.0]
config file = /home/user/ansible/ansible.cfg
configured module search path = ['/home/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/user/ansible/.venv/lib/python3.13/site-packages/ansible
ansible collection location = /home/user/.ansible/collections:/usr/share/ansible/collections
executable location = /home/user/ansible/.venv/bin/ansible
python version = 3.13.7 (main, Aug 20 2025, 22:17:40) [GCC 15.2.0] (/home/user/ansible/.venv/bin/python3)
jinja version = 3.1.6
pyyaml version = 6.0.3 (with libyaml v0.2.5)

Ansible Galaxy

/home/user/.ansible/collections/ansible_collections

Collection	Version
arubanetworks.aoscx	4.4.0

Python

Python 3.13.7

Pip

Package	Version
ansible	13.0.0
ansible-core	2.20.0
ansible-pylibssh	1.3.0
bcrypt	5.0.0
certifi	2025.11.12
cffi	2.0.0
charset-normalizer	3.4.4
cryptography	46.0.3
idna	3.11
invoke	2.2.1
Jinja2	3.1.6
MarkupSafe	3.0.3
netaddr	1.3.0
normalizer	0.2.1
packaging	25.0
paramiko	4.0.0
pip	25.3
pyaoscx	2.6.0
pycparser	2.23
pycurl	7.45.7
PyNaCl	1.6.1
PyYAML	6.0.3
requests	2.32.5
requests-toolbelt	1.0.0
resolvelib	1.2.1
setuptools	80.9.0
urllib3	2.5.0
wheel	0.45.1

[alagoutte]

can you try with this playbook :

- hosts: switch-test
  collections:
    - arubanetworks.aoscx
  gather_facts: false
  tasks:
    - name: Create VLAN 550 with description and name
      aoscx_vlan:
        vlan_id: 550
        name: test_VLAN
        description: This is VLAN 550

your yaml look not valid (indent issue for -name)

[LeFouineur]

can you try with this playbook :

• hosts: switch-test
  collections:
  • arubanetworks.aoscx
    gather_facts: false
    tasks:
  • name: Create VLAN 550 with description and name
    aoscx_vlan:
    vlan_id: 550
    name: test_VLAN
    description: This is VLAN 550
    your yaml look not valid (indent issue for -name)

It was when I copied the file in GH, a space was missing, but the original YAML is valid and the same as your indentations.
I edited my OP to fix the formatting.

(I also tried with yours, just to be sure and still the same error)

[LeFouineur]

I just tested, I'm now able to SSH whitout error (one lib-dev seemed to have been missing before).

But when I try in REST API, I still have my error, but I can see the modification present on the device.

It would seem that the problem is on parsing the return informations from the switch.

I have the problem on firmwares 10.15.1020 & 10.16.1010, at least.

[tchiapuziowong]

@LeFouineur I believe this error is seen with the changes introduced in Ansible 2.19 - if you install Ansible 2.18 or lower it should resolve that error?