germalight.blogg.se - Ssh connect to host port 22 network is unreachable linux

Task path: /tmp/awx_14021_ypwngn_h/project/test.yml:91 I can see that every SSH connection method is tested, and it ends in error: with additional characters, no LF at the end of the private key file, etc.), the task that is supposed to trigger the user works and ends in error.

with an invalid public/private keys (ie.

Here it's frozen, nothing more in the AWX output, nothing in the remote host SSH logs. SSH: EXEC sshpass -d12 ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKe圜hecking=no -o 'IdentityFile=".dummy_pk_random_name"' -o 'User="ssh_user_B"' -o ConnectTimeout=10 -o ControlPath=/tmp/awx_14019_pqypcw0i/cp/bc63f1e109 target_remote_host '/bin/sh -c '"'"'echo ~ssh_user_B & sleep 0'"'"'' ESTABLISH SSH CONNECTION FOR USER: ssh_user_B Wait_for_connection: attempting ping module test Task path: /tmp/awx_14019_pqypcw0i/project/test.yml:91 "ansible_ssh_private_key_file": ".dummy_pk_random_name", Task path: /tmp/awx_14019_pqypcw0i/project/test.yml:83 ESTABLISH LOCAL CONNECTION FOR USER: root Task path: /tmp/awx_14019_pqypcw0i/project/test.yml:57

ESTABLISH SSH CONNECTION FOR USER: ssh_user_A Task path: /tmp/awx_14019_pqypcw0i/project/test.yml:2 with valid public/private keys, the task that is supposed to trigger the user change seems frozen at the first SSH connection attempt, nothing more happens, and nothing in the target remote host SSH logs (in these logs, I have the connection for the ssh_user_A, but absolutely nothing for the ssh_user_B one)ĪWX output: PLAYBOOK: test.yml *************************************************************.

I change the SSH user in the playbook with these instructions: - name: Switch to ssh_user_B userĪnsible_ssh_pass: ""Īnd the user change is triggered by a simple wait_for_connection: - name: Just here to validate the user changeīut unfortunately, the only thing that I get is a behavior that I do not understand:

if I test this public/private key with a temp machine credentials (not possible in final target) and a dummy playbook or an ad-hoc module call, it works I can do whatever I need.the public key is present on the remote host in the ~ssh_user_B/.ssh/authorized_keys file.a public/private keys couple for ssh_user_B:.machine credentials for ssh_user_A that are OK, I can do whatever I need.In this playbook, i need to perform a couple of tasks with another SSH user, ie. I have a playbook that is launched from AWX with machine credentials, ie.