yahoo-eng-team team mailing list archive

[OpenStack Infra <1774710@xxxxxxxxxxxxxxxxxx>]

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

commit 137a6d61053fb1cfb9a0a583b5a5c0f6253c75e6
Author: Assaf Muller <amuller@xxxxxxxxxx>
Date:   Thu May 31 14:24:00 2018 -0400

    Pass network's dns_domain to dnsmasq conf
    
    The Neutron API exposes the 'dns_domain' attribute on the
    Network model. Presently, deployments using the DHCP
    agent ignore this attribute when resolving DNS queries
    between instances. This patch changes that so that
    the DHCP agent will pass on the dns_domain to the
    network's dnsmasq process, in turn passing it to
    instances.
    
    UpgradeImpact
    Closes-Bug: 1774710
    Change-Id: I6120d504959631f084d63458f6e9dada0dc5cbdf


** 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/1774710

Title:
  DHCP agent doesn't do anything with a network's dns_domain attribute

Status in neutron:
  Fix Released

Bug description:
  0) Set up Neutron with ML2/OVS or LB, or anything that uses the DHCP agent
  1) Create a network with dns_domain
  2) Boot a VM on it

  Notice the VM doesn't have the DNS domain in it's /etc/resolv.conf

  In short, per-network DNS domains are not respected by the DHCP agent.
  The dns_domain attribute is persisted in the Neutron DB and passed on
  to the DHCP agent via RPC, but the agent doesn't do anything with it.

  Versions:
  Master and all previous versions.

  WIP fix is in https://review.openstack.org/#/c/571546.

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