yahoo-eng-team team mailing list archive

[OpenStack Infra <1746000@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/538929
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d3c69dc4f22ef96ad3fb66430ce703d9c2199d2e
Submitter: Zuul
Branch:    master

commit d3c69dc4f22ef96ad3fb66430ce703d9c2199d2e
Author: Dirk Mueller <dirk@xxxxxxxx>
Date:   Mon Jan 29 15:11:04 2018 +0100

    Drop strict-order flag from dnsmasq invocation
    
    Without this flag, dnsmasq prefers to ask the servers that
    are known to be up, rather than hitting servers that are either
    down or known to be broken. This greatly reduces responsivity
    impact of broken upstream servers.
    
    Closes-Bug: #1746000
    Change-Id: Ieee4dafc578c3bda0935fcdb80faad6c342a10e9


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1746000

Title:
  dnsmasq does not fallback on SERVFAIL

Status in neutron:
  Fix Released

Bug description:
  In our cloud deployment, we configured neutron-dhcp-agent
  to have multiple external DNS servers

  However, the last server on the list happened to be misconfigured (by others). So it returned SERVFAIL instead of correct responses and strace showed that dnsmasq only ever asked the last server for a name.
  My testing shows that dropping the --strict-order parameter helped this problem.
  It was introduced in commit 43960ee448 without reason given.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1746000/+subscriptions