yahoo-eng-team team mailing list archive

[OpenStack Infra <1541192@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

https://review.openstack.org/269822
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 003091a97480f12ea2fe948b6b9d8b4646d9463f
Author: armando-migliaccio <armamig@xxxxxxxxx>
Date:   Tue Jan 19 11:25:05 2016 -0800

    Set default value for dnsmasq_local_resolv to False
    
    patch 0de1d8d4c introduced a new behavior whereby dnsmasq can rely
    on dns resolvers defined in the host's resolv.conf, and it did
    that by default.
    
    However this may introduce dns timeouts if the dns servers
    are not reachable for whatever reason. This may be especially
    likely in certain gate configurations (where the VM under test
    is a guest itself).
    
    Regardless of the root-cause analysis, this option should have
    defaulted to False to preserve backward compatibility, therefore
    this patch restores the old behavior in a way that local DNS
    resolution occurs only if the new option variable is set to
    True, or the admin has not explicitly set the list of DNS
    servers to be injected in the DHCP response.
    
    DocImpact: document how to configure DNS resolution by dnsmasq
    
    Change-Id: I90ab26bfa83c2d23c92110b8da73ef771e11f7bb

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

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

Title:
      Set default value for dnsmasq_local_resolv to False

Status in neutron:
  New

Bug description:
  https://review.openstack.org/269822
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 003091a97480f12ea2fe948b6b9d8b4646d9463f
  Author: armando-migliaccio <armamig@xxxxxxxxx>
  Date:   Tue Jan 19 11:25:05 2016 -0800

      Set default value for dnsmasq_local_resolv to False
      
      patch 0de1d8d4c introduced a new behavior whereby dnsmasq can rely
      on dns resolvers defined in the host's resolv.conf, and it did
      that by default.
      
      However this may introduce dns timeouts if the dns servers
      are not reachable for whatever reason. This may be especially
      likely in certain gate configurations (where the VM under test
      is a guest itself).
      
      Regardless of the root-cause analysis, this option should have
      defaulted to False to preserve backward compatibility, therefore
      this patch restores the old behavior in a way that local DNS
      resolution occurs only if the new option variable is set to
      True, or the admin has not explicitly set the list of DNS
      servers to be injected in the DHCP response.
      
      DocImpact: document how to configure DNS resolution by dnsmasq
      
      Change-Id: I90ab26bfa83c2d23c92110b8da73ef771e11f7bb

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