Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2184040

Summary: FRR cannot be restarted alone
Product: Red Hat OpenStack Reporter: Eduardo Olivares <eolivare>
Component: ovn-bgp-agentAssignee: Luis Tomas Bolivar <ltomasbo>
Status: CLOSED ERRATA QA Contact: Candido Campos <ccamposr>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: dalvarez, lmartins, ltomasbo
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovn-bgp-agent-0.3.1-1.20230422171003.2553998.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:14:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eduardo Olivares 2023-04-03 13:33:28 UTC 
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.
Comment 16 errata-xmlrpc 2023-08-16 01:14:34 UTC 
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