Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1399577 - [3.4] dnsmasq should not set strict-order
[3.4] dnsmasq should not set strict-order
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Scott Dodson
Johnny Liu
:
: 1399756 (view as bug list)
Depends On:
Blocks: 1400130 1400139 1400686
  Show dependency tree / graph
 
Reported: 2016-11-29 05:37 EST by Johnny Liu
Modified: 2017-03-08 13 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously the dnsmasq configuration included "strict-order" which meant that dnsmasq would iterate through the host's nameservers in order. This meant that if the first nameserver had failed a lengthy timeout is observed while dnsmasq waits before moving on to the next nameserver. By removing the strict-order option dnsmasq will prefer nameservers that it knows to be up over those which are unresponsive ensuring faster name resolution. If you wish add this or any other option please use the advanced installer option 'openshift_node_dnsmasq_additional_config_file' which allows you to provide the path to a dnsmasq configuration file that will be deployed on all nodes.
Story Points: ---
Clone Of:
: 1400130 (view as bug list)
Environment:
Last Closed: 2017-01-18 07:56:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Comment 6 Scott Dodson 2016-11-30 08:39:30 EST 
*** Bug 1399756 has been marked as a duplicate of this bug. ***
Comment 10 Johnny Liu 2016-12-05 01:49:32 EST 
Waiting to get errata puddle including the fix PR.
Comment 11 Johnny Liu 2016-12-07 05:39:46 EST 
Verified this bug with openshift-ansible-3.4.35-1.git.0.2e13650.el7, and PASS.

After installation, check:
# cat /etc/dnsmasq.d/origin-dns.conf 
no-resolv
domain-needed
server=/cluster.local/172.30.0.1

# cat /etc/dnsmasq.d/origin-upstream-dns.conf 
server=192.168.2.2
server=10.11.11.11


All the dns could be resolved by both 192.168.2.2 and 10.11.11.11.
Comment 13 errata-xmlrpc 2017-01-18 07:56:10 EST 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0066
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.