Bug 1370610

Summary: Intermittent Pod DNS Issues
Product: OpenShift Container Platform Reporter: Steven Walter <stwalter>
Component: NodeAssignee: Derek Carr <decarr>
Status: CLOSED DUPLICATE QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: aos-bugs, eparis, erich, jokerman, mmccomas, stwalter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-30 14:08:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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