ansible-playbook [core 2.17.14] 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-miH executable location = /usr/local/bin/ansible-playbook python version = 3.12.12 (main, Nov 14 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-14)] (/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 Skipping callback 'debug', as we already have a stdout callback. Skipping callback 'json', as we already have a stdout callback. Skipping callback 'jsonl', 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_misc.yml ******************************************************* 1 plays in /tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml PLAY [Test misc features of the storage role] ********************************** TASK [Gathering Facts] ********************************************************* task path: /tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml:2 Friday 02 January 2026 11:53:24 -0500 (0:00:00.032) 0:00:00.032 ******** [WARNING]: Platform linux on host managed-node10 is using the discovered Python interpreter at /usr/bin/python3.9, 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-node10] TASK [Include the role to ensure packages are installed] *********************** task path: /tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml:15 Friday 02 January 2026 11:53:25 -0500 (0:00:01.107) 0:00:01.140 ******** ERROR! the role 'fedora.linux_system_roles.storage' was not found in fedora.linux_system_roles:ansible.legacy:/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage The error appears to be in '/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml': line 17, column 15, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: include_role: name: fedora.linux_system_roles.storage ^ here fatal: [managed-node10]: FAILED! => { "changed": false, "reason": "the role 'fedora.linux_system_roles.storage' was not found in fedora.linux_system_roles:ansible.legacy:/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage\n\nThe error appears to be in '/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml': line 17, column 15, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n include_role:\n name: fedora.linux_system_roles.storage\n ^ here\n" } PLAY RECAP ********************************************************************* managed-node10 : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 SYSTEM ROLES ERRORS BEGIN v1 [ { "ansible_version": "2.17.14", "end_time": "2026-01-02T16:53:25.509805+00:00Z", "host": "managed-node10", "message": "No message could be found", "start_time": "2026-01-02T16:53:25.494629+00:00Z", "task_name": "Include the role to ensure packages are installed", "task_path": "/tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml:15" } ] SYSTEM ROLES ERRORS END v1 TASKS RECAP ******************************************************************** Friday 02 January 2026 11:53:25 -0500 (0:00:00.016) 0:00:01.157 ******** =============================================================================== Gathering Facts --------------------------------------------------------- 1.11s /tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml:2 Include the role to ensure packages are installed ----------------------- 0.02s /tmp/collections-miH/ansible_collections/fedora/linux_system_roles/tests/storage/tests_misc.yml:15 Jan 02 11:53:24 managed-node10 sudo[18244]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-tniathzeotiiizdzrkisqtkyvyxpcbfc ; /usr/bin/python3.9 /root/.ansible/tmp/ansible-tmp-1767372804.4263656-30489-191658413325028/AnsiballZ_setup.py' Jan 02 11:53:24 managed-node10 sudo[18244]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0) Jan 02 11:53:25 managed-node10 python3.9[18246]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jan 02 11:53:25 managed-node10 sudo[18244]: pam_unix(sudo:session): session closed for user root Jan 02 11:53:25 managed-node10 sshd-session[18306]: Accepted publickey for root from 10.31.15.184 port 40658 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jan 02 11:53:25 managed-node10 systemd-logind[594]: New session 79 of user root. ░░ Subject: A new session 79 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 79 has been created for the user root. ░░ ░░ The leading process of the session is 18306. Jan 02 11:53:25 managed-node10 systemd[1]: Started Session 79 of User root. ░░ Subject: A start job for unit session-79.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-79.scope has finished successfully. ░░ ░░ The job identifier is 6271. Jan 02 11:53:25 managed-node10 sshd-session[18306]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jan 02 11:53:25 managed-node10 sshd-session[18309]: Received disconnect from 10.31.15.184 port 40658:11: disconnected by user Jan 02 11:53:25 managed-node10 sshd-session[18309]: Disconnected from user root 10.31.15.184 port 40658 Jan 02 11:53:25 managed-node10 sshd-session[18306]: pam_unix(sshd:session): session closed for user root Jan 02 11:53:25 managed-node10 systemd[1]: session-79.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-79.scope has successfully entered the 'dead' state. Jan 02 11:53:25 managed-node10 systemd-logind[594]: Session 79 logged out. Waiting for processes to exit. Jan 02 11:53:25 managed-node10 systemd-logind[594]: Removed session 79. ░░ Subject: Session 79 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 79 has been terminated. Jan 02 11:53:25 managed-node10 sshd-session[18334]: Accepted publickey for root from 10.31.15.184 port 40672 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jan 02 11:53:25 managed-node10 systemd-logind[594]: New session 80 of user root. ░░ Subject: A new session 80 has been created for user root ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A new session with the ID 80 has been created for the user root. ░░ ░░ The leading process of the session is 18334. Jan 02 11:53:25 managed-node10 systemd[1]: Started Session 80 of User root. ░░ Subject: A start job for unit session-80.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-80.scope has finished successfully. ░░ ░░ The job identifier is 6340. Jan 02 11:53:25 managed-node10 sshd-session[18334]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)