[OVN] Old DNS servers are served by DHCP after dns_servers option is updated
Bug #1983270 reported by
Pierre Riteau
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Confirmed
|
Medium
|
Elvira García Ruiz | ||
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-
Version:
* OpenStack Wallaby
* CentOS Stream 8
* Deployed with Kolla
| Changed in neutron: | |
| status: | New → Confirmed |
| Changed in neutron: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Elvira García Ruiz (elviragr) |
To post a comment you must log in.
