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

Bug 1823993

Summary:	etcd: fix deadlock in grpclb connection cache
Product:	OpenShift Container Platform	Reporter:	Sam Batschelet <sbatsche>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	dmace, mfojtik, skolicha
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: gRPC-go 1.23.0 had a bug in client loadbalancer Consequence: This could result in deadlock Fix: gRPC-go is bumped to use patched v1.23.1 Result: The conditions for client loadbalancer resulting in deadlock are no longer there.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:27:56 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 Sam Batschelet 2020-04-15 02:02:05 UTC

Description of problem: gRPC-go 1.23.0 had a bug in client loadbalancer which could result in deadlock[1]

[1] https://github.com/grpc/grpc-go/pull/3017


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: gRPC-go is unpatched v1.23.0


Expected results: gRPC-go is bumped to use patched v1.23.1


Additional info:

Comment 2 Michal Fojtik 2020-05-18 07:29:25 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 9 errata-xmlrpc 2020-07-13 17:27:56 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, 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/RHBA-2020:2409