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

Bug 1878123

Summary:	Action required: Update the cluster-logging-operator and elasticsearch-operator to client-go v1.18.8
Product:	OpenShift Container Platform	Reporter:	Periklis Tsirakidis <periklis>
Component:	Logging	Assignee:	Periklis Tsirakidis <periklis>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	logging-core, logging-exploration
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 15:10:28 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 Periklis Tsirakidis 2020-09-11 11:55:25 UTC

Description of problem:
[aos-devel] [Action required] components/operators vendoring client-go 1.18
Lukasz Szaszkiewicz <lszaszki>

11:39 AM (2 hours ago)

to aos-devel

Hi all

I would like to draw your attention to a recent fix in the reflector/informer https://github.com/kubernetes/kubernetes/pull/92688 that has been merged upstream.

Without it, your component/operator might enter a hot loop and stuck. There are already reported cases that have run into that issue and were stuck for hours or even days.

For example https://bugzilla.redhat.com/show_bug.cgi?id=1877346.

The root cause of the issue is the fact that a watch cache is initialized from the global revision (etcd) and might stay on it for an undefined period (if no changes were (add, modify) made).

That means that the watch cache across server instances may be out of sync.

That might lead to a situation in which a client gets a resource version from a server that has observed a newer rv, disconnect (due to a network error) from it, and reconnect to a server that is behind, resulting in “Too large resource version“ errors.

You will find more details in https://github.com/kubernetes/kubernetes/issues/91073 and https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/1904-efficient-watch-resumption

It looks like the issue only affects 1.18. According to https://github.com/kubernetes/kubernetes/issues/91073#issuecomment-652251669 the issue was first introduced in that version by changes done to the reflector.

The fix is already present in 1.19.

So if you are on 1.18 please make sure you update to a version that includes https://github.com/kubernetes/kubernetes/pull/92688

Comment 1 Jeff Cantrill 2020-09-12 01:53:07 UTC

Moving to UpcomingSprint awaiting for PRs to merge, etc.

Comment 5 errata-xmlrpc 2020-10-27 15:10:28 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.6.1 extras 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:4198