[Bug 1826419] Fix merged to neutron (stable/queens)

[OpenStack Infra]

Reviewed:  https://review.opendev.org/663293
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8c7c26c5bdb87ab7c30b5b50ec925c49ac4c01d4
Submitter: Zuul
Branch:    stable/queens

commit 8c7c26c5bdb87ab7c30b5b50ec925c49ac4c01d4
Author: James Page <james.page at ubuntu.com>
Date:   Mon Jun 3 09:38:16 2019 +0100

    Revert "Pass network's dns_domain to dnsmasq conf"
    
    The dns_domain attribute of a network is intended for use
    by neutron when creating DNS records in an external DNS
    system such as Designate.
    
    By using the networks dns_domain, the configured search
    path on booted instances mismatches with the generated
    dns assignments for instance ports in the hosts file
    for dnsmasq which creates a mismatched forward/reverse
    lookup behaviour.
    
    This reverts commit 28b90f6c14659500694f321eedbf313d83a2ae9c.
    
    Change-Id: I26b5e8c35233718d97e58cfd5735c62d1684b4b0
    Closes-Bug: 1826419
    Depends-On: I145144c042b100f7e12a02a8ac7e0fbbe41e984d

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1826419

Title:
  dhcp agent configured with mismatching domain and host entries

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive queens series:
  Fix Committed
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Bionic:
  Fix Committed
Status in neutron source package in Cosmic:
  Fix Committed
Status in neutron source package in Disco:
  Fix Committed
Status in neutron source package in Eoan:
  Fix Released

Bug description:
  Related bug 1774710 and bug 1580588

  The neutron-dhcp-agent in OpenStack >= Queens makes use of the
  dns_domain value set on a network to configure the '--domain'
  parameter of the dnsmasq instance that supports it;  at the same time,
  neutron makes use of CONF.dns_domain when creating dns_assignments for
  ports - this results in a hosts file for the dnsmasq instance which
  uses CONF.dns_domain and a --domain parameter of network.dns_domain
  which do not match.

  This results in a search path on instances booted attached to the
  network which is inconsistent with the internal DNS entries that
  dnsmasq responds with:

    root at bionic-045546-2:~# host 192.168.21.222
    222.21.168.192.in-addr.arpa domain name pointer bionic-045546-2.jamespage.internal.
    root at bionic-045546-2:~# host bionic-045546-2
    bionic-045546-2.designate.local has address 192.168.21.222

  In the above example:

    CONF.dns_domain = jamespage.internal.
    network.dns_domain = designate.local.

  Based on previous discussion in bug 1580588 I think that the
  dns_domain value for a network was intented for use for external DNS
  integration such as that provided by Designate.

  The changed made under commit:

    https://opendev.org/openstack/neutron/commit/137a6d61053

  appear to break this assumption, producing somewhat inconsistent
  behaviour in the dnsmasq instance for the network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1826419/+subscriptions