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

Bug 1892596

Summary:	SDN pods failing to list due to "Too large resource version"
Product:	OpenShift Container Platform	Reporter:	jnaess
Component:	Networking	Assignee:	Jacob Tanenbaum <jtanenba>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	aconstan, lszaszki
Version:	4.5
Target Milestone:	---
Target Release:	4.7.0
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-03 14:25:53 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 jnaess 2020-10-29 09:43:25 UTC

Description of problem:
Alert KubeAPIErrorsHigh firing due to SDN pods failing to list resources, due to "Too large resource version

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

How reproducible:
unsure

Steps to Reproduce:
1.
2.
3.

Actual results:
sdn-gxbwj.log:2288:E1028 10:29:16.481666 1853544 reflector.go:178] runtime/asm_amd64.s:1357: Failed to list *v1.NetworkPolicy: Timeout: Too large resource version: 218848897, current: 218843265
sdn-ngz4g.log:2422:E1028 10:30:04.309226 2948441 reflector.go:178] runtime/asm_amd64.s:1357: Failed to list *v1.Namespace: Timeout: Too large resource version: 218853563, current: 218843252


Expected results:
No timeouts due to "too large resource version"

Additional info:
must-gather in progress

Comment 3 Lukasz Szaszkiewicz 2020-11-02 16:53:31 UTC

May I know we did you change the target release? This issue must be fixed in 4.5

Comment 4 Jacob Tanenbaum 2020-11-03 14:25:53 UTC


*** This bug has been marked as a duplicate of bug 1880341 ***