Actions
Bug #15466
closed"ERROR:paramiko.transport:Socket exception: Connection timed out"
Status:
Closed
Priority:
Urgent
Assignee:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
teuthology
Crash signature (v1):
Crash signature (v2):
Description
Seems to be ovh specific
Run: http://pulpito.ovh.sepia.ceph.com:8081/teuthology-2016-04-11_22:24:06-teuthology-master---basic-openstack/
Jobs: all dead
Logs: http://teuthology.ovh.sepia.ceph.com/teuthology/teuthology-2016-04-11_22:24:06-teuthology-master---basic-openstack/33966/teuthology.log
016-04-11T22:50:37.525 ERROR:paramiko.transport:Socket exception: Connection timed out (110) 2016-04-12T00:45:13.693 INFO:teuthology.task.ansible.out:[0;31mfatal: [target091251.ovh.sepia.ceph.com] => SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh[0m
Updated by Dan Mick about 8 years ago
Sure looks like ovh became unresponsive. Any contradictory evidence to that theory?
Updated by Yuri Weinstein about 8 years ago
run manually a failed test and could not reproduce it after 8 time (with the hammer.sh)
Updated by Kevin Lamontagne almost 8 years ago
The OVH Anti-DDoS firewall drops the first SSH connection when it's active. It happened to some systems I have hosted there in early April. It's not really documented but there is a blog about it (search for "SSH"). Maybe that has something to do with it.
Actions