# Ansible for network automation

**URL:** <https://forum.ansible.com/t/ansible-for-network-automation/39479>\
**Category:** Get Help\
**Tags:** ansible\
**Created:** [January 6, 2025, 2:40pm UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479 "2025-01-06T14:40:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinod\_Kumar6](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/vinod_kumar6/32/7141_2.png) [@Vinod\_Kumar6](https://forum.ansible.com/u/Vinod_Kumar6)\
**Post date:** [January 6, 2025, 2:40pm UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479/1 "2025-01-06T14:40:41Z")

</div>

Hi Team,

When I am using shell module to access remote device and running commands on device using shell , giving me error "failed to resolve remote temporary directory from ansible-tmp-…

Please anyone help me on same  
Regards  
Vinod

---

<div class="post-metadata">

**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\
**Post date:** [January 7, 2025, 12:53am UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479/2 "2025-01-07T00:53:05Z")

</div>

There isn’t much to go on from this post, but if you’re trying to do a shell operation on a network device like a router or switch, the device probably does not have enough of an OS to support what shell needs. You should look for modules that are specific towards your hardware and vendor use-case.

---

<div class="post-metadata">

**Author:** ![Vinod\_Kumar6](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/vinod_kumar6/32/7141_2.png) [@Vinod\_Kumar6](https://forum.ansible.com/u/Vinod_Kumar6)\
**Post date:** [January 7, 2025, 2:22pm UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479/3 "2025-01-07T14:22:07Z")

</div>

Thank you for your response  
But earlier my playbook was working fine, but after some os upgrade on the jump server I am having the issues

Please find attached error screenshot

 ![1000022207](https://us1.discourse-cdn.com/ansible/original/2X/c/cd89c4fb2c5bf3cc7aaba6d6d79f2cf713ad7b4d.jpeg)

---

<div class="post-metadata">

**Author:** ![motorbass](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@motorbass](https://forum.ansible.com/u/motorbass)\
**Post date:** [January 7, 2025, 2:25pm UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479/4 "2025-01-07T14:25:56Z")

</div>

As we’re not diviner, let us know what your playbook look like if you need proper help 🙂

---

<div class="post-metadata">

**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\
**Post date:** [January 7, 2025, 11:14pm UTC](https://forum.ansible.com/t/ansible-for-network-automation/39479/5 "2025-01-07T23:14:14Z")

</div>

I’m not sure what the reason would be to paste the error message into a word document and then take a picture of your computer screen with your phone’s camera, but if you want people to help you, you need to make it easy on them to do so.

Please take the time to post the actual error message in here, and use the backticks to make it readable for others (it’d also be good to run your playbook in verbose mode for extra info, removing any sensitive data before posting). It would also make things easier for people to understand what’s going on if you pasted your playbook in here. It would also be helpful if you would explain your network topology since it seems like you’re using a jump server.

You mention it worked “earlier” but then an OS upgrade happened. We don’t work at your company, so we can’t really use this information to any effect. Maybe the OS upgrade had something to do with it, but you already suspected that. What have you done to troubleshoot the issue on your side? Have you tried running that failing command you pasted into the word doc on your computer screen on the target machine (or maybe the jump server)?