Running playbook returns: Failed to connect to the host via ssh, solved by running ping all

Question

I have an ansible playbook and I run it:

sudo ansible-playbook -i hosts startelk.yml -vvv

Every time, after I change the hosts file, running the same playbook results in "Failed to connect to the host via ssh". If I run

ansible all -m ping

first and then the playbook command, the playbook gets successfully started.

Does anyone know why do I have to run ping each time after changing hosts (or some other) file, and then my ssh connection for playbook works, otherwise no? I don't want to be running ping every time I need to change something in Ansible.

Thanks!

There are hundreds "ansible ssh" issues at SO. Follow How to create a Minimal, Complete, and Verifiable example. — Vladimir Botka
– Vladimir Botka, Commented Apr 9, 2019 at 8:57

Vladimir Botka · Accepted Answer · 2019-04-09 11:56:14Z

2

It's not a good idea to run "sudo ansible-playbook ..." This way the controller connects the host as root. Best practice is not to allow root ssh connections.

Best practice is to:

run ansible-playbook as a normal user
configure remote_user and
escalate the privilege with become and become_user.

Read more at Understanding Privilege Escalation.

edited Apr 9, 2019 at 11:56

answered Apr 9, 2019 at 8:56

Vladimir Botka

69.9k7 gold badges45 silver badges78 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Amela Over a year ago

You're right, sudo was the problem, didn't know it makes the controller connect as root. Now it works, thanks!

Collectives™ on Stack Overflow

Running playbook returns: Failed to connect to the host via ssh, solved by running ping all

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related