ansible-playbook [core 2.17.12]
  config file = None
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.12/site-packages/ansible
  ansible collection location = /tmp/collections-m9y
  executable location = /usr/local/bin/ansible-playbook
  python version = 3.12.10 (main, May  9 2025, 00:00:00) [GCC 14.2.1 20250110 (Red Hat 14.2.1-7)] (/usr/bin/python3.12)
  jinja version = 3.1.6
  libyaml = True
No config file found; using defaults
running playbook inside collection fedora.linux_system_roles
statically imported: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/set_selinux_variables.yml
statically imported: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/set_selinux_variables.yml
statically imported: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/set_selinux_variables.yml
statically imported: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/set_selinux_variables.yml
Skipping callback 'debug', as we already have a stdout callback.
Skipping callback 'default', as we already have a stdout callback.
Skipping callback 'minimal', as we already have a stdout callback.
Skipping callback 'oneline', as we already have a stdout callback.

PLAYBOOK: tests_login.yml ******************************************************
1 plays in /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/tests_login.yml

PLAY [Check if selinux role sets SELinux login mappings] ***********************

TASK [Gathering Facts] *********************************************************
task path: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/tests_login.yml:2
Tuesday 17 June 2025  14:29:08 -0400 (0:00:00.021)       0:00:00.021 ********** 
[WARNING]: Platform linux on host managed-node1 is using the discovered Python
interpreter at /usr/bin/python3.12, but future installation of another Python
interpreter could change the meaning of that path. See
https://docs.ansible.com/ansible-
core/2.17/reference_appendices/interpreter_discovery.html for more information.
ok: [managed-node1]

TASK [Add a System Api Roles SELinux User] *************************************
task path: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/tests_login.yml:5
Tuesday 17 June 2025  14:29:09 -0400 (0:00:01.192)       0:00:01.214 ********** 
changed: [managed-node1] => {
    "append": false,
    "changed": true,
    "comment": "System Api Roles SELinux User",
    "group": 1000,
    "home": "/home/sar-user",
    "move_home": false,
    "name": "sar-user",
    "shell": "/bin/bash",
    "state": "present",
    "uid": 1000
}

TASK [Initial changes] *********************************************************
task path: /tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/tests/selinux/tests_login.yml:10
Tuesday 17 June 2025  14:29:10 -0400 (0:00:00.557)       0:00:01.771 ********** 
redirecting (type: modules) ansible.builtin.selinux to ansible.posix.selinux
ERROR! couldn't resolve module/action 'selinux'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/tmp/collections-m9y/ansible_collections/fedora/linux_system_roles/roles/selinux/tasks/main.yml': line 29, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  block:
    - name: Set permanent SELinux state if enabled
      ^ here