Bug 1400686 - [3.1] dnsmasq should not set strict-order
Summary: [3.1] dnsmasq should not set strict-order
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.1.1
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1399577 1400130
Blocks: 1400139
TreeView+ depends on / blocked
 
Reported: 2016-12-01 20:07 UTC by Scott Dodson
Modified: 2016-12-01 20:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1400130
Environment:
Last Closed: 2016-12-01 20:24:19 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 1 Scott Dodson 2016-12-01 20:07:53 UTC 
https://github.com/openshift/openshift-ansible/pull/2905
Comment 4 Scott Dodson 2016-12-01 20:24:19 UTC 
Not going to fix this for 3.1, it doesn't have the newer logic that makes dnsmasq the only resolver.
Note You need to log in before you can comment on or make changes to this bug.