Public bug reported:
As documented in https://docs.openstack.org/neutron/latest/admin/config-
dns-res.html#case-1-each-virtual-network-uses-unique-dns-resolver-s ,
setting dns-nameserver=0.0.0.0 for a subnet should indicate that DHCP
should not advertise any DNS server to instances on that subnet. This
works fine with LB or OVS, but with OVN, instead the IP 0.0.0.0 is
advertised as nameserver to instances.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: ovn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1950686
Title:
[OVN] dns-nameserver=0.0.0.0 for a subnet isn't treated properly
Status in neutron:
New
Bug description:
As documented in
https://docs.openstack.org/neutron/latest/admin/config-dns-
res.html#case-1-each-virtual-network-uses-unique-dns-resolver-s ,
setting dns-nameserver=0.0.0.0 for a subnet should indicate that DHCP
should not advertise any DNS server to instances on that subnet. This
works fine with LB or OVS, but with OVN, instead the IP 0.0.0.0 is
advertised as nameserver to instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1950686/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
