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

Bug 2102673

Summary:	FRR start race condition
Product:	OpenShift Container Platform	Reporter:	Federico Paolinelli <fpaoline>
Component:	Networking	Assignee:	Federico Paolinelli <fpaoline>
Networking sub component:	Metal LB	QA Contact:	Arti Sood <asood>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	high	CC:	cgoncalves
Version:	4.12	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-17 19:51:09 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:
Bug Depends On:
Bug Blocks:	2115813

Description Federico Paolinelli 2022-06-30 12:30:46 UTC

Description of problem:

If the configuration is already in place, and the speaker container is faster than the frr or the frr reloader container to start, the speaker won't apply the configuration until the next change.

Version-Release number of selected component (if applicable):


How reproducible:
Hardly, I was able to reproduce it by injecting sleeps in the frr / frr-reloader entry points. It was found by an upstream user who had the cpu throttled down. Upstream issue: https://github.com/metallb/metallb/issues/1462

Additional info:

Comment 2 Carlos Goncalves 2022-07-04 08:11:52 UTC

Fixed upstream in main branch. Patch will be brought downstream at the next rebase.
Patch needs to be ported back to OCP 4.10.z.

Comment 8 errata-xmlrpc 2023-01-17 19:51:09 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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), 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/RHSA-2022:7399

Comment 9 Red Hat Bugzilla 2023-09-18 04:40:46 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days