[Bug 1826419] Related fix merged to neutron-tempest-plugin (master)

[OpenStack Infra]

Reviewed:  https://review.opendev.org/662713
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=e142c0b6e9d935ec37bdcab4efbca7c2ca9b150e
Submitter: Zuul
Branch:    master

commit e142c0b6e9d935ec37bdcab4efbca7c2ca9b150e
Author: James Page <james.page at ubuntu.com>
Date:   Mon Jun 3 09:23:40 2019 +0100

    Ensure DNS configuration from conf
    
    For internal DNS the DNS configuration including the search
    path should be derived from configuration rather than from
    the dns_domain attribute of the network, which is used for
    external DNS integration.
    
    Update test to ensure that configuration based dns domain
    is present in the server search path and is used to validate
    resolution of the hostname of the server.
    
    This commit also temporaily skips the internal DNS test whilst
    the associated Neutron reviews are landed; it will be re-enabled
    afterwards.
    
    Change-Id: I145144c042b100f7e12a02a8ac7e0fbbe41e984d
    Related-Bug: 1826419
    Required-By: I5ff03b5ad8af432a9f7919ef953d7d8c434b93bd

-- 
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:
  In Progress
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