[ATMOSPHERE-606] replace value of dnsmasq_dns_servers to 1.1.1.1 #2184
Conversation
mnaser
changed the title
roles/neutron/vars/main.yml
Outdated
| @@ -60,7 +60,7 @@ __neutron_helm_values: | |||
| service_provider: VPN:strongswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default | |||
| dhcp_agent: | |||
| DEFAULT: | |||
| dnsmasq_dns_servers: "{{ neutron_coredns_cluster_ip | default('10.96.0.20') }}" | |||
| dnsmasq_dns_servers: "{{ neutron_coredns_cluster_ip | default('1.1.1.1') }}" | |||
There was a problem hiding this comment.
When using ML2/OVS, the 10.96.0.20 works just fine, but when using ML2/OVN we need to use 1.1.1.1.
There was a problem hiding this comment.
I reverted back for ML2/OVS to 10.96.0.20
There was a problem hiding this comment.
We can simply add this:
dnsmasq_dns_servers: "{{ neutron_coredns_cluster_ip | default('1.1.1.1') }}"
Into the OVN section, since that gets merged into the OVN part.
Also, perhaps I think we should add a variable called neutron_default_dns_servers which gets set to 10.96.0.20 if its not using ovn, and by default, do not set it, so the user has to set it if its using ovn.
There was a problem hiding this comment.
I added dnsmasq_dns_servers to OVN part. And for neutron_default_dns_servers I put it on neutron conf for ML2/OVS part. I'm not sure if it was correct or not. Need your feedback @mnaser
…s variable to neutron conf for ML2/OVS
The bug was detected when customer env use OVN and they got 10.96.0.20 for nameserves from DHCP Agent. We can unset in on atmosphere/roles/neutron/vars/main.yml at main · vexxhost/atmosphere line 63 or replace that value with public DNS, e.g. 1.1.1.1.