Project

General

Profile

Actions

Bug #44343

closed

opensuse.org not accessible from Sepia lab hosts

Added by Nathan Cutler about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
% Done:

0%

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

Description

After today's reboot of the teuthology VM, it seems no hosts in the "opensuse.org" domain are reachable from the Sepia lab:

(virtualenv) smithfarm@teuthology:~$ hostname --fqdn
teuthology.front.sepia.ceph.com
(virtualenv) smithfarm@teuthology:~$ ping www.opensuse.org
ping: unknown host www.opensuse.org
(virtualenv) smithfarm@teuthology:~$ ping download.opensuse.org
ping: unknown host download.opensuse.org
(virtualenv) smithfarm@teuthology:~$ ping www.google.com
PING www.google.com (172.217.9.196) 56(84) bytes of data.
64 bytes from iad30s14-in-f4.1e100.net (172.217.9.196): icmp_seq=1 ttl=50 time=7.94 ms
^C
--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.946/7.946/7.946/0.000 ms
(virtualenv) smithfarm@teuthology:~$ ping www.redhat.com
PING e3396.dscx.akamaiedge.net (23.1.49.220) 56(84) bytes of data.
64 bytes from a23-1-49-220.deploy.static.akamaitechnologies.com (23.1.49.220): icmp_seq=1 ttl=55 time=7.91 ms
64 bytes from a23-1-49-220.deploy.static.akamaitechnologies.com (23.1.49.220): icmp_seq=2 ttl=55 time=7.81 ms
^C
--- e3396.dscx.akamaiedge.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 7.816/7.864/7.912/0.048 ms

(I can ping these hosts from my laptop, of course.)

Actions #2

Updated by Nathan Cutler about 4 years ago

  • Description updated (diff)
Actions #3

Updated by Nathan Cutler about 4 years ago

  • Subject changed from After reboot of teuthology VM, can no longer reach *.opensuse.org to opensuse.org not accessible from Sepia lab hosts
Actions #4

Updated by David Galloway about 4 years ago

The teuthology VM actually never got rebooted (it didn't need to be). And I can't reproduce this. Is it possible it was a temporary public DNS hiccup?

Actions #5

Updated by Nathan Cutler about 4 years ago

  • Status changed from New to Closed

The problem went away over the weekend :-D

Actions

Also available in: Atom PDF