yahoo-eng-team team mailing list archive

[Pierre Riteau <1983270@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

To adapt to updated DNS servers used by the OpenStack cloud, the
following option was used in ml2_conf.ini:

[ovn]
dns_servers = <DNS1>,<DNS2>

However, instances (including new ones) are still getting the old DNS
servers from DHCP on a subnet with an empty dns_nameservers property.

I found that the ovn/dns_servers configuration option is used only when
there is a change to the subnet. I managed to have it taken into account
by applying a dummy update to the subnet:

openstack subnet set demo --dns-nameserver 192.168.0.1
openstack subnet set demo --no-dns-nameservers

Version:

* OpenStack Wallaby
* CentOS Stream 8
* Deployed with Kolla

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  [OVN] Old DNS servers are served by DHCP after dns_servers option is
  updated

Status in neutron:
  New

Bug description:
  To adapt to updated DNS servers used by the OpenStack cloud, the
  following option was used in ml2_conf.ini:

  [ovn]
  dns_servers = <DNS1>,<DNS2>

  However, instances (including new ones) are still getting the old DNS
  servers from DHCP on a subnet with an empty dns_nameservers property.

  I found that the ovn/dns_servers configuration option is used only
  when there is a change to the subnet. I managed to have it taken into
  account by applying a dummy update to the subnet:

  openstack subnet set demo --dns-nameserver 192.168.0.1
  openstack subnet set demo --no-dns-nameservers

  Version:

  * OpenStack Wallaby
  * CentOS Stream 8
  * Deployed with Kolla

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