Documentation #44905
Updated by Sebastian Wagner about 4 years ago
<pre>
<wowas> I'm getting:
<wowas> execnet.gateway_bootstrap.HostNotFound: -F /tmp/cephadm-conf-kbqvkrkw root@10.10.1.2
<wowas> raise OrchestratorError('Failed to connect to %s (%s). Check that the host is reachable and accepts connections using the cephadm SSH key' % (host, addr)) from e
<wowas> orchestrator._interface.OrchestratorError: Failed to connect to 10.10.1.2 (10.10.1.2). Check that the host is reachable and accepts connections using the cephadm SSH key
</pre>
Things users can do:
1. ensure, we can connect to the host via ssh:
<pre>
[root@mon1 ~]# cephadm shell -- ceph config-key get mgr/cephadm/ssh_identity_key > key
INFO:cephadm:Inferring fsid f8edc08a-7f17-11ea-8707-000c2915dd98
INFO:cephadm:Using recent ceph image docker.io/ceph/ceph:v15
obtained 'mgr/cephadm/ssh_identity_key'
[root@mon1 ~]# chmod 0600 key
</pre>
If this fails, cephadm doesn't have a key. Fix this by:
<pre>
[root@mon1 ~]# cephadm shell -- ceph cephadm generate-ssh-key
</pre>
or
<pre>
[root@mon1 ~]# cat key | cephadm shell -- ceph cephadm set-ssk-key -i - ...
</pre>
2. ensure the ssh config is correct
<pre>
[root@mon1 ~]# cephadm shell -- ceph cephadm get-ssh-config > config
</pre>
3. Verify we can connect to the host:
<pre>
[root@mon1 ~]# ssh -F config -i key root@mon1
ssh: connect to host mon1 port 22: Connection timed out
</pre>
4. There is a limitation right now. the ssh user is root. Hardcoded.