Why does Ansible Automation Platform fail to connect to managed nodes in the 10.0.2.x subnet during playbook execution?

Solution Verified - Updated -

Issue

  • How to resolve the following error while launching Jobs in Automation Controller:

    <managed-node> SSH: EXEC sshpass -d12 ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o 'User="ansible"' -o ConnectTimeout=10 -o 'ControlPath="/home/runner/.ansible/cp/f02793dc34"' <managed-node> '/bin/sh -c '"'"'echo ~ansible && sleep 0'"'"''
    <managed-node> (255, b'', b'ssh: connect to host <managed-node>port 22: No route to host\r\n')
    IP 10.0.2.91 of <managed-node> managed node
    

Environment

  • Red Hat® Ansible Automation Platform

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content