Score:0

Ansible freeze on connect in Gathering Facts

br flag

I run the Ansible Playbook via Jenkins, but the role freezes when connected. I generated a couple of keys. I put the public key in the target server (/root/.ssh/) and set the private key in Jenkins incl. passphrase.

PLAYBOOK: dns.yml **************************************************************
[0;34m1 plays in /var/lib/jenkins/workspace/Ansible - DNS autoconfigurator/dns.yml[0m

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
[1;30mtask path: /var/lib/jenkins/workspace/Ansible - DNS autoconfigurator/dns.yml:2[0m
[0;34m<server.test> ESTABLISH SSH CONNECTION FOR USER: root[0m
[0;34m<server.test> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o 'IdentityFile="/tmp/ssh15103930497671545526.key"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o ControlPath=/var/lib/jenkins/.ansible/cp/6293757a61 server.test '/bin/sh -c '"'"'echo ~root && sleep 0'"'"''[0m

I added the -vvv parameter, can you please tell someone what I'm doing wrong?

Thanks for the information.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.