yahoo-eng-team team mailing list archive

[Neil Jerram <neil@xxxxxxxxx>]

The corresponding Neutron agent code is also still using dhcp_domain in
stable/newton and current master.

** Summary changed:

- Calico DHCP agent should use DEFAULT/dns_domain instead of DEFAULT/dhcp_domain
+ DHCP agent should use DEFAULT/dns_domain instead of DEFAULT/dhcp_domain

** Project changed: networking-calico => 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/1646802

Title:
  DHCP agent should use DEFAULT/dns_domain instead of
  DEFAULT/dhcp_domain

Status in neutron:
  New

Bug description:
  
  As of Mitaka, DEFAULT/dhcp_domain in neutron.conf seems to be deprecated, the neutron now uses DEFAULT/dns_domain.

  http://docs.openstack.org/mitaka/config-
  reference/networking/networking_options_reference.html

  
  With Calico DHCP agent, unless we create the deprecated option DEFAULT/dhcp_domain in neutron.conf, the instances resolv.conf contains:
    domain openstacklocal
    search openstacklocal

  ..instead of the desired domain name.

  It could potentially check for both config options, and make
  dns_domain tape precedence over dhcp_domain.


  Cheers,
  Just

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