Skip to main content

Please add this host's fingerprint to your known_hosts file to manage this host

Error: -
192.168.43.216 | FAILED! => {
    "msg": "Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this.  Please add this host's fingerprint to your known_hosts file to manage this host."
}
 If you get above error message on Ansible controller that means your managed host are not added to known hosts. You can fix this issue in two way: -
1. Add "host_key_checking = false" in ansible.cfg(best practice)
[root@ansible ssh]# cat >> /etc/ansible/ansible.cfg
host_key_checking = false

Let's check if issue has been fixed, If I am getting "ping": "pong" response that mean the issue has been fixed.
[root@ansible ssh]# ansible all -m ping
192.168.43.72 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/libexec/platform-python"
    },
    "changed": false,
    "ping": "pong"
}
192.168.43.216 | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/libexec/platform-python"
    },
    "changed": false,
    "ping": "pong"
}

2. Initiate ssh connection and Accept ssh fingerprint: - As we know by default Ansible need ssh connection between controller node and managed node and when first time someone try to ssh any host, we have accept connection fingerprint just for very first time only.
[root@ansible ~]# ssh 192.168.43.216
The authenticity of host '192.168.43.216 (192.168.43.216)' can't be established.
ECDSA key fingerprint is SHA256:Os7z03gBEm2OZz1Cjy/yQ5j+Eyrj4FMlnQxlvDoe7Lk.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
root@192.168.43.216's password: ***********
[root@managed-node2 ~]#

That's how you can fix this issue.

Labels

Labels:

Comments

Post a Comment

Please share your experience.....

Popular posts from this blog

error: db5 error(11) from dbenv->open: Resource temporarily unavailable

If rpm command is not working in your system and it is giving an error message( error: db5 error(11) from dbenv->open: Resource temporarily unavailable ). What is the root cause of this issue? How to fix this issue?   just a single command- [root@localhost rpm]# rpm --rebuilddb Detailed error message- [root@localhost rpm]# rpm -q firefox ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db5 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages database in /var/lib/rpm package firefox is not installed [root@localhost rpm]# RPM manage a database in which it store all information related to packages installed in our system. /var/lib/rpm, this is directory where this information is available. [root@localhost rpm]# cd /var/lib/rpm ...
2 comments
Read more

Failed to get D-Bus connection: Operation not permitted

" Failed to get D-Bus connection: Operation not permitted " - systemctl command is not working in Docker container. If systemctl command is not working in your container and giving subjected error message then simple solution of this error is, create container with -- privileged option and also provide init file full path  /usr/sbin/init [root@server109 ~]# docker container run -dit --privileged --name systemctl_not_working_centos1 centos:7 /usr/sbin/init For detailed explanation and understanding I am writing more about it, please have look below. If we have a daemon based program(httpd, sshd, jenkins, docker etc.) running inside a container and we would like to start/stop or check status of daemon inside docker then it becomes difficult for us to perform such operations , because by default systemctl and service  commands don't work inside docker. Normally we run below commands to check services status in Linux systems. [root@server109 ~]# systemctl status ...
4 comments
Read more

error: src refspec main does not match any

$ git push -u origin main error: src refspec main does not match any error: failed to push some refs to 'https://gitlab.com/jay2tinku/my-new-project.git' If you get such error while performing any git operation. This means you have to check your default branch name. From last few git versions by default branch name is main instead of master . It never means that it will always be main/master . Normally at the time of installation we have to configure that but most of the time we ignore that and go with default options. Simple fix of this error is :- git push -u origin master or git push -u origin main Please have a look on below scenario for complete understanding $ mkdir my-new-project $ cd  my-new-project $ git status $ git init $ cat > test.txt My first line!!! $  git status $ git remote add origin https://gitlab.com/jay2tinku/my-test-project.git $ git add . $ git status $ git commit . -m "Intial push commit" $ git push -u origin main error: src...
1 comment
Read more