networking-ovn doesn't define a default dns_server option in the DHCP_Options table for subnets without dns_nameservers defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Undecided
|
Numan Siddique | ||
tripleo |
Fix Released
|
Medium
|
Numan Siddique |
Bug Description
This is a behavioural difference with ml2/ovs and the dhcp-agent.
In the reference implementation, when a subnet is created, if no dns servers is provided the dhcp resolution will point to the dnsmasq port instance, which will resolv internal dns requests, and forward the unknown ones upstream.
In the case of networking-ovn, we don't create a dhcp port for dhcp purposes. We just capture instance outgoing DNS queries, and respond to the internal ones, while the external ones are sent back to network. such implementation requires that at least one dns server has been configured via DHCP to the instance. But if during subnet creation the dns-server / dns-servers field was left unspecified, the internal dns server won't work.
A temporary workaround is configuring the upstream dns server when creating the subnet:
neutron subnet-update 4db68a2b-
Changed in networking-ovn: | |
assignee: | nobody → Numan Siddique (numansiddique) |
status: | New → In Progress |
description: | updated |
Changed in tripleo: | |
assignee: | nobody → Numan Siddique (numansiddique) |
status: | New → In Progress |
Changed in tripleo: | |
importance: | Undecided → Medium |
milestone: | none → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Fix proposed to branch: master /review. openstack. org/571006
Review: https:/