UNREACHABLE error while running an Ansible playbook

Question

I do have access to ssh into the destination machine, and it works, but whenever I run this playbook, I get this error output:

sudo ansible-playbook ansible-playbook-test.yml

PLAY [openstack] *****************************************************************************************************************************************************************************************

TASK [Gathering Facts] ***********************************************************************************************************************************************************************************
fatal: [amachine]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive).\r\n", "unreachable": true}
        to retry, use: --limit @/blah/ansible-play/ansible-playbook-test.retry

PLAY RECAP ***********************************************************************************************************************************************************************************************
amachine       : ok=0    changed=0    unreachable=1    failed=0

My playbook is as simple as this:

---
# hosts could have been "remote" or "all" as well

- hosts: openstack
  tasks:
    - name: test connection
      ping:
      remote_user: djuarezg
      vars:
        ansible_ssh_extra_args: '-K -o ControlPath=none'



- hosts: openstack
  tasks:
    - name: Create Swarm cluster
      command: mkdir djg
      vars:
        ansible_ssh_extra_args: '-K -o ControlPath=none'

I was trying to use ansible_ssh_extra_args: '-K -o ControlPath=none' to see if it was able to forward the Kerberos ticket, but any kind of connection is enough.

how is the ssh authentication supposed to work? u have ssh-keys exchanged for user `djuarezg`? — ilias-sp, Jun 14 '18 at 17:48

score 7 · Accepted Answer · answered Jun 15 '18 at 21:50

7

Try this:

$ ansible-playbook --user=djuarezg -vvv ansible-playbook-test.yml

Check SSH args in the output

answered Jun 15 '18 at 21:50

Panic

2,229
23
25

score 5 · Answer 2 · answered Mar 05 '21 at 10:58

5

This worked for me:

$ cd /root/.ssh
$ ssh-keygen -t rsa

save key under the name of id_rsa

$ cat id_rsa.pub

copy the entire key and paste in file (of master node located at path: /.ssh/ or /root/.ssh) as:

$ sudo nano authorized_keys

Then run this to check:

$ ansible all -m ping -u root

Output should be like this:

master-node | SUCCESS => {
    "changed": false,
    "ping": "pong"
}

answered Mar 05 '21 at 10:58

Hamza Saeed

164
1
15

1

This worked for me too. Was trying to install diaspora on an Rpi and this got me unstuck from that same unreachable error. – Josh P Mar 13 '23 at 20:50

Michael Zietlow · Answer 3 · 2020-11-20T22:38:57.600

2

I had a similar issue with large host inventories through jumpboxes. Mine was set high to speed up large plays but it didn't play nicely when introducing a jump box and I hit this random Unreachable issue.

The solution was to reduce the amount forks.
15 was okay but 10 was the sweet spot for my env...

edited Nov 20 '20 at 22:38

answered Nov 20 '20 at 18:59

Michael Zietlow

71
7

score 1 · Answer 4 · answered Oct 06 '20 at 12:09

1

Adding user designation fixed it for me - -u deploy

ansible-playbook [...yml] -u deploy

answered Oct 06 '20 at 12:09

Alex Buznik

686
1
6
26

UNREACHABLE error while running an Ansible playbook

4 Answers4

Linked