Description of problem: After restarting the FRR service on any compute or controller, part of the FRR configuration is missed. This is because the ovn_bgp_agent adds the required VRF configuration to the running FRR service. So, there is a simple workaround: to restart the ovn_bgp_agent after restarting FRR. In order to manage HA scenarios (FRR dies unexpectedly and tripleo restarts it), the agent's sync process will add the VRF configuration section (sync is executed periodically): https://review.opendev.org/c/x/ovn-bgp-agent/+/879326 Version-Release number of selected component (if applicable): RHOS-17.1-RHEL-9-20230315.n.1 How reproducible: 100% Steps to Reproduce: 1. systemctl restart tripleo_frr (on any overcloud node) 2. 3. Actual results: Routes to some running VMs are not advertised after FRR is restarted. Expected results: Routes to all running VMs should be advertised after FRR is restarted.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577