Bug 1446067 - Name resolution failed after restarting openshift-master
Summary: Name resolution failed after restarting openshift-master
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-27 08:08 UTC by Kenjiro Nakayama
Modified: 2017-04-28 14:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 14:33:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.