Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1446067

Summary:	Name resolution failed after restarting openshift-master
Product:	OpenShift Container Platform	Reporter:	Kenjiro Nakayama <knakayam>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Status:	CLOSED NOTABUG	QA Contact:	Meng Bo <bmeng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.1	CC:	aos-bugs
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:	2017-04-28 14:33:05 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:
Embargoed:

Description Kenjiro Nakayama 2017-04-27 08:08:25 UTC

Description of problem:
---
After restarting openshift master, dnsmasq stopped forwarding the query to some of upstream DNS servers. Then, it failed to solve the hostname and also failed to start OpenShift Nodes and Masters due to no such host.

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

How reproducible:
---
- This issue cannot produceable. Sometimes happened.

Steps to Reproduce:
---
1. Restart atomic-openshift-master

Actual results:
---
- Failed to solve the hostname, due to no such host.

Expected results:
---
- OpenShift correctly starts.

Additional info:
---
- We collected dnsmasq query logs when the issue happened.