Bug 1370610 - Intermittent Pod DNS Issues
Summary: Intermittent Pod DNS Issues
Keywords:
Status: CLOSED DUPLICATE of bug 1351645
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Derek Carr
QA Contact: DeShuai Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-26 18:55 UTC by Steven Walter
Modified: 2020-05-14 15:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-30 14:08:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Steven Walter 2016-08-26 18:55:25 UTC 
Description of problem:

DNS at the container level is intermittently failing. Usually, the DNS works (is able to use kubernetes.default.svc.cluster.local to resolve access.redhat.com, etc) but occasionally stops.


Version-Release number of selected component (if applicable):
3.2.0

How reproducible:
Have not been able to reproduce yet

Steps to Reproduce:
1. rsh into pod
2. nslookup kubernetes.default.svc.cluster.local

Actual results:
About 1/10 times will say nslookup: can't resolve 'kubernetes.default.svc.cluster.local': Name does not resolve

Otherwise:
Name:      kubernetes.default.svc.cluster.local
Address 1: 172.30.0.1

Expected results:
Only results in:
Name:      kubernetes.default.svc.cluster.local
Address 1: 172.30.0.1

Additional info:
See private comment, next
Note You need to log in before you can comment on or make changes to this bug.