Project

General

Profile

Actions
Copy link

Bug #8581

closed

DNS issues when resolving hosts

Added by Alfredo Deza almost 10 years ago. Updated over 9 years ago.

Status:
Can't reproduce
Priority:
Normal
Assignee:
Sandon Van Ness
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

There have been consistent DNS errors where some hosts cannot be resolved and end up causing
failures with ceph-deploy tests.

2014-06-10T15:06:50.675 INFO:teuthology.orchestra.run.err:[10.214.138.70]: ssh: Could not resolve hostname vpm073: No address associated with hostname
2014-06-10T15:06:50.675 INFO:teuthology.orchestra.run.err:[10.214.138.70]: [ceph_deploy.osd][ERROR ] connecting to host: vpm073 resulted in errors: HostNotFound vpm073
2014-06-10T15:06:50.675 INFO:teuthology.orchestra.run.err:[10.214.138.70]: [ceph_deploy][ERROR ] GenericError: Failed to create 1 OSDs

This is not specific to ceph-deploy tests.

Actions
Copy link
 #1

Updated by Alfredo Deza almost 10 years ago

Still seeing DNS issues:

2014-06-29T12:06:54.552 INFO:teuthology.orchestra.run.vpm020.stderr:[ceph_deploy][ERROR ] RuntimeError: connecting to host: vpm059 resulted in errors: HostNotFound vpm059

Log file: http://qa-proxy.ceph.com/teuthology/teuthology-2014-06-29_01:11:54-ceph-deploy-firefly-distro-basic-vps/332415/teuthology.log

Actions
Copy link
 #2

Updated by Sandon Van Ness almost 10 years ago

Despite what that error message says right before that it shows a 'no route to host' which is not a DNS error:

2014-06-29T12:06:51.552 INFO:teuthology.orchestra.run.vpm020.stderr:ssh: connect to host vpm059 port 22: No route to host
Actions
Copy link
 #3

Updated by Sage Weil over 9 years ago

  • Status changed from New to Can't reproduce
Actions
Copy link

Also available in: Atom PDF