From 4d91920e5f6fc5dde67b4a6befeaebc6337332ce Mon Sep 17 00:00:00 2001 From: Martin Kennelly Date: Sat, 14 Jun 2025 10:24:48 +0100 Subject: [PATCH] Networking: reset ovn-remote config and allow ovnkube controller to set it This fixes the issue where ovn-remote is set prior to reboot and when boot occurs, ovn-controller syncs quickly with a stale SB DB. This PR is part of the EIP GARP issue fix. Its required because when ovnkube-controller and ovn-controller container start on boot, there is no order to which container will start first, and we dont want ovn-controller to connect to SB DB before ovnkube controller has added the drop flows. Ideally, we would only allow ovn-controller to sync with SB DB when ovnkube controller has concluded syncing and the changes are available in SB DB. That maybe future work. Signed-off-by: Martin Kennelly --- templates/common/_base/files/configure-ovs-network.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/templates/common/_base/files/configure-ovs-network.yaml b/templates/common/_base/files/configure-ovs-network.yaml index ff924592aa..a45b9f6f42 100644 --- a/templates/common/_base/files/configure-ovs-network.yaml +++ b/templates/common/_base/files/configure-ovs-network.yaml @@ -5,6 +5,13 @@ contents: #!/bin/bash set -x + # Clear ovn-remote config to connect to OVN DBs. + # ovnkube controller will set it on startup. + # May remove when https://issues.redhat.com/browse/FDP-1537 is availabe + # However it may also be a good idea to leave this because we don't want + # ovn-controller syncing to a stale OVN southbound database. + ovs-vsctl set Open_vSwitch . external_ids:ovn-remote=" " + if [ -e /etc/nmstate/openshift/applied ]; then echo "Skipping configure-ovs due to manual network configuration" exit 0