Bug 1884192

Summary: kuryr-controller stuck if connection to K8s API dies silently
Product: OpenShift Container Platform Reporter: Luis Tomas Bolivar <ltomasbo>
Component: NetworkingAssignee: Luis Tomas Bolivar <ltomasbo>
Networking sub component: kuryr QA Contact: GenadiC <gcheresh>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: gcheresh, itbrown, mdulko
Version: 4.6   
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1884139 Environment:
Last Closed: 2020-10-19 14:55:01 UTC Type: ---
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: 1884139    
Bug Blocks:    
Attachments:
Description Flags
Kuryr controller log none

Description Luis Tomas Bolivar 2020-10-01 10:03:09 UTC
+++ This bug was initially created as a clone of Bug #1884139 +++

Kuryr components are often contacting the K8s API through a loadbalancer (e.g. Octavia LB in DevStack deployments, HAProxy in OpenShift) and we've often seen they're able to drop connections silently, effectively leaving our requests hanging forever. This got fixed in `K8sClient.watch` by setting a read timeout there which helped a lot, but we now seem to see it happening with other requests that doesn't have read timeout set.

Comment 3 Itzik Brown 2020-10-14 10:31:17 UTC
4.5.0-0.nightly-2020-10-10-030038
RHOS-16.1-RHEL-8-20201005.n.0
Attached the log from kuryr controller. Verified it times out.

Comment 4 Itzik Brown 2020-10-14 10:33:00 UTC
Created attachment 1721444 [details]
Kuryr controller log

Comment 6 errata-xmlrpc 2020-10-19 14:55:01 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 (OpenShift Container Platform 4.5.15 bug fix 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/RHBA-2020:4228