# Unable to execute ansible-test network-integration command on ansible 2.19

**URL:** <https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205>\
**Category:** Get Help\
**Created:** [June 6, 2025, 10:58am UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205 "2025-06-06T10:58:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![trisha-dell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trisha-dell/32/8640_2.png) [@trisha-dell](https://forum.ansible.com/u/trisha-dell)\
**Post date:** [June 6, 2025, 10:58am UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205/1 "2025-06-06T10:58:46Z")

</div>

I am unable to execute playbooks using ansible-test network-integration command on ansible-core 2.19.0b5.  
I have used the ansible.builtin.include\_tasks command and passed a .yml file, which in turn performs some tasks.  
When I do so, I get an error stating the file is not found for the file passed in the include\_tasks command.

```auto
- name: Check the firmware version
  ansible.builtin.include_tasks: _check_firmware_version_supported.yml

```

Here I get the following error:  
[Errno 2] No such file or directory

I have also exported the ANSIBLE\_COLLECTIONS\_PATH and PYTHONPATH variables.

What am I missing here?

---

<div class="post-metadata">

**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\
**Post date:** [June 6, 2025, 11:38am UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205/2 "2025-06-06T11:38:46Z")

</div>

Is the file with the `include_tasks` directive in the same directory as the `_check_firmware_version_supported.yml` file?

If not could you explain, or illustrate via the use of `tree`, your file structure?

If the file is from a different role perhaps you need to use [include\_role](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/include_role_module.html) with a [tasks\_from](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/include_role_module.html#parameter-tasks_from) for `_check_firmware_version_supported`?

---

<div class="post-metadata">

**Author:** ![trisha-dell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trisha-dell/32/8640_2.png) [@trisha-dell](https://forum.ansible.com/u/trisha-dell)\
**Post date:** [June 6, 2025, 3:20pm UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205/3 "2025-06-06T15:20:30Z")

</div>

Hello Chris,  
Thank you for responding.  
Yes, my file belongs to the same directory.  
This playbook is not calling any roles.

I have observed this issue only in Ansible Core 2.19 (I have tested it on Ansible 2.19.0b3 and 2.19.0b5 ).  
This has worked fine for me in the 2.18 version of Ansible

---

<div class="post-metadata">

**Author:** ![mattclay](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mattclay/32/268_2.png) [@mattclay](https://forum.ansible.com/u/mattclay)\
**Post date:** [June 6, 2025, 4:41pm UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205/4 "2025-06-06T16:41:30Z")

</div>

@trisha-dell Can you open a bug report and provide a reproducer?

---

<div class="post-metadata">

**Author:** ![trisha-dell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trisha-dell/32/8640_2.png) [@trisha-dell](https://forum.ansible.com/u/trisha-dell)\
**Post date:** [June 9, 2025, 9:26am UTC](https://forum.ansible.com/t/unable-to-execute-ansible-test-network-integration-command-on-ansible-2-19/43205/5 "2025-06-09T09:26:45Z")

</div>

I have raised a GitHub issue, please let me know if anything else is needed.

> <https://github.com/ansible/ansible/issues/85282>
>
> \### Summary
> 
> I am unable to execute playbooks using ansible-test network-integra…tion command on ansible-core 2.19.0b5.
> I have used the ansible.builtin.include\_tasks command and passed a .yml file, which in turn performs some tasks.
> When I do so, I get an error stating the file is not found for the file passed in the include\_tasks command.
> 
> This executes fine in older version of Ansible (2.18.x and below)
> 
> \### Issue Type
> 
> Bug Report
> 
> \### Component Name
> 
> ansible.builtin.include\_tasks
> 
> \### Ansible Version
> 
> \`\`\`console
> ansible \[core 2.19.0b5\]
> config file = /etc/ansible/ansible.cfg
> configured module search path = \['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'\]
> ansible python module location = /home/Trisha/OMAM/ans\_219\_py\_312/lib/python3.12/site-packages/ansible
> ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
> executable location = /home/Trisha/OMAM/ans\_219\_py\_312/bin/ansible
> python version = 3.12.1 (main, Jan 29 2025, 03:25:41) \[GCC 11.5.0 20240719 (Red Hat 11.5.0-2)\] (/home/Trisha/OMAM/ans\_219\_py\_312/bin/python3.12)
> jinja version = 3.1.6
> pyyaml version = 6.0.2 (with libyaml v0.2.5)
> \`\`\`
> 
> \### Configuration
> 
> \`\`\`console
> CONFIG\_FILE() = /etc/ansible/ansible.cfg
> 
> GALAXY\_SERVERS:
> \`\`\`
> 
> \### OS / Environment
> 
> Operating System: Red Hat Enterprise Linux 9.5 (Plow)
> 
> \### Steps to Reproduce
> 
> A yaml playbook containing the following task is executed using the command:
> ansible-test network-integration \<module\_name\> --test \<test\_case\_name\> -vvv
> \`\`- name: Check the firmware version
> ansible.builtin.include\_tasks: \_check\_firmware\_version\_supported.yml
> \`\`\`
> 
> 
> \### Expected Results
> 
> The expectation is that the file executes and the data returned(register variables of the tasks) is in JSON format, as returned from the task.
> 
> \### Actual Results
> 
> \`\`\`console
> \[Errno 2\] No such file or directory
> \`\`\`
> 
> \### Code of Conduct
> 
> \- \[x\] I agree to follow the Ansible Code of Conduct
