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-oAZ executable location = /usr/local/bin/ansible-playbook python version = 3.12.11 (main, Aug 14 2025, 00:00:00) [GCC 14.3.1 20250617 (Red Hat 14.3.1-2)] (/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_stratis.yml **************************************************** 1 plays in /tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml PLAY [Test stratis pool management] ******************************************** TASK [Gathering Facts] ********************************************************* task path: /tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml:2 Friday 02 January 2026 11:52:24 -0500 (0:00:00.045) 0:00:00.045 ******** [WARNING]: Platform linux on host managed-node10 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-node10] TASK [Run the role] ************************************************************ task path: /tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml:14 Friday 02 January 2026 11:52:25 -0500 (0:00:01.166) 0:00:01.211 ******** ERROR! the role 'fedora.linux_system_roles.storage' was not found in fedora.linux_system_roles:ansible.legacy:/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage The error appears to be in '/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml': line 16, 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-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage\n\nThe error appears to be in '/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml': line 16, 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:52:25.512454+00:00Z", "host": "managed-node10", "message": "No message could be found", "start_time": "2026-01-02T16:52:25.499288+00:00Z", "task_name": "Run the role", "task_path": "/tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml:14" } ] SYSTEM ROLES ERRORS END v1 TASKS RECAP ******************************************************************** Friday 02 January 2026 11:52:25 -0500 (0:00:00.014) 0:00:01.225 ******** =============================================================================== Gathering Facts --------------------------------------------------------- 1.17s /tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml:2 Run the role ------------------------------------------------------------ 0.01s /tmp/collections-oAZ/ansible_collections/fedora/linux_system_roles/tests/storage/tests_stratis.yml:14 Jan 02 11:52:24 managed-node10 sudo[21983]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c 'echo BECOME-SUCCESS-klznnoggthohsnwbaypnotlojypsegnd ; /usr/bin/python3.12 /root/.ansible/tmp/ansible-tmp-1767372744.3767102-36630-166051048886944/AnsiballZ_setup.py' Jan 02 11:52:24 managed-node10 sudo[21983]: pam_unix(sudo:session): session opened for user root(uid=0) by root(uid=0) Jan 02 11:52:25 managed-node10 python3.12[21986]: ansible-ansible.legacy.setup Invoked with gather_subset=['all'] gather_timeout=10 filter=[] fact_path=/etc/ansible/facts.d Jan 02 11:52:25 managed-node10 sudo[21983]: pam_unix(sudo:session): session closed for user root Jan 02 11:52:25 managed-node10 sshd-session[22049]: Accepted publickey for root from 10.31.9.135 port 46666 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jan 02 11:52:25 managed-node10 systemd-logind[757]: New session 101 of user root. ░░ Subject: A new session 101 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 101 has been created for the user root. ░░ ░░ The leading process of the session is 22049. Jan 02 11:52:25 managed-node10 systemd[1]: Started session-101.scope - Session 101 of User root. ░░ Subject: A start job for unit session-101.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-101.scope has finished successfully. ░░ ░░ The job identifier is 9192. Jan 02 11:52:25 managed-node10 sshd-session[22049]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0) Jan 02 11:52:25 managed-node10 sshd-session[22052]: Received disconnect from 10.31.9.135 port 46666:11: disconnected by user Jan 02 11:52:25 managed-node10 sshd-session[22052]: Disconnected from user root 10.31.9.135 port 46666 Jan 02 11:52:25 managed-node10 sshd-session[22049]: pam_unix(sshd:session): session closed for user root Jan 02 11:52:25 managed-node10 systemd[1]: session-101.scope: Deactivated successfully. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ The unit session-101.scope has successfully entered the 'dead' state. Jan 02 11:52:25 managed-node10 systemd-logind[757]: Session 101 logged out. Waiting for processes to exit. Jan 02 11:52:25 managed-node10 systemd-logind[757]: Removed session 101. ░░ Subject: Session 101 has been terminated ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ Documentation: sd-login(3) ░░ ░░ A session with the ID 101 has been terminated. Jan 02 11:52:25 managed-node10 sshd-session[22078]: Accepted publickey for root from 10.31.9.135 port 46676 ssh2: RSA SHA256:9j1blwt3wcrRiGYZQ7ZGu9axm3cDklH6/z4c+Ee8CzE Jan 02 11:52:25 managed-node10 systemd-logind[757]: New session 102 of user root. ░░ Subject: A new session 102 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 102 has been created for the user root. ░░ ░░ The leading process of the session is 22078. Jan 02 11:52:25 managed-node10 systemd[1]: Started session-102.scope - Session 102 of User root. ░░ Subject: A start job for unit session-102.scope has finished successfully ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit session-102.scope has finished successfully. ░░ ░░ The job identifier is 9274. Jan 02 11:52:25 managed-node10 sshd-session[22078]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)