From ce3a70dbc76868fcd6604de6edbf2679fd3bd95d Mon Sep 17 00:00:00 2001 From: Doug Goldstein Date: Mon, 22 Dec 2025 20:02:03 -0600 Subject: [PATCH] fix(neutron): fix c9a394172 which still didn't work DNS resolution does not work with OVS prior to 3.4.0 and Ubuntu Noble ships with 3.3.4. Neutron uses newer libraries but it calls out to the ovsdb-client CLI from the distro and that's where things fall apart. --- components/neutron/values.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/components/neutron/values.yaml b/components/neutron/values.yaml index bae37a9ca..d12a5b331 100644 --- a/components/neutron/values.yaml +++ b/components/neutron/values.yaml @@ -58,11 +58,13 @@ conf: # OSH sets a default range here but we want to use network_segment_range plugin # to configure this instead vni_ranges: "" - ovn: + ovn: {} # remove this when we upgrade to a chart with # https://review.opendev.org/c/openstack/openstack-helm/+/971656 - ovn_nb_connection: "tcp:ovn-ovsdb-nb.openstack.svc:6641" - ovn_sb_connection: "tcp:ovn-ovsdb-sb.openstack.svc:6642" + # DNS resolution does not work in OVS prior to 3.4.0 and noble + # uses 3.3.4. This is just a problem for the ovsdb-client CLI calls + #ovn_nb_connection: "tcp:ovn-ovsdb-nb.openstack.svc:6641" + #ovn_sb_connection: "tcp:ovn-ovsdb-sb.openstack.svc:6642" neutron: DEFAULT: # https://docs.openstack.org/neutron/latest/admin/config-wsgi.html