Ansible deploy playbooks in eve-ng lab through linux jump-server [EVE-NG Professional Edition]

[eliaspy]

Hi all!

we've purchased the EVE-NG-PRO version and have build a topology of 2 vSRX , 2 vQFX and a Linux ubuntu machine that we trying to use as a Jump-Server and use it with my local machine as an Ansible Controller to get to the remotes host inside the eve-ng lab. until this point I'm not able to send playbooks through the Linux Jump-Server. at this point I have configured the following:

1.- SSH connectivity from Linux jump-server to my local machine ( shared ssh keys)
2.- Set the ansible_ssh_common_args= ' ProxyCommand="ssh -W %h:%p localadmin@jump-server-ip. in the ansible invenrory file
3.- ping and SSH reachability from linux jump-server to junos vSRX and vQFX.
4.- NETCONF configured in all junos devices inside the lab.
|
currently I'm facing this error:

#### 192.168.255.129 = vSRX

The full traceback is:
File "/home/Users/.ansible/collections/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py", line 233, in get_capabilities
capabilities = Connection(module._socket_path).get_capabilities()
File "/usr/lib/python3/dist-packages/ansible/module_utils/connection.py", line 200, in __rpc__
raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code)
fatal: [192.168.255.129]: FAILED! => {
"changed": false,
"invocation": {
"module_args": {
"available_network_resources": false,
"config_format": "set",
"gather_network_resources": null,
"gather_subset": [
"config"
]
}
},
"msg": "Could not open socket to 192.168.255.129:830"
}

PLAY RECAP *****************************************************************************************************
192.168.255.129 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0



Please my team and I will appreciate any support,

thanks in advance!

[eliaspy]

SOLVED!

we had configured the 'ansible_netconf_ssh_config' variable pointing to the ssh config file path
- ansible_netconf_ssh_config: ~home/User/.ssh/config

although there is more than one way to accomplish and it is covered in the doc below:

- https://docs.ansible.com/ansible/latest ... oxycommand
- https://blog.networktocode.com/post/ans ... tion-host/

[mayomayo72218]

Thank you for this workaround!
Super Mario

[Sition]

SOLVED!

we had configured the 'ansible_netconf_ssh_config' variable pointing to the ssh config file path
- ansible_netconf_ssh_config: ~home/User/.ssh/config

although there is more than one way to accomplish and it is covered in the doc below:

- https://docs.ansible.com/ansible/latest ... oxycommand
- https://blog.networktocode.com/post/ans ... tion-host/

Thanks for this