Bug 1892596 - SDN pods failing to list due to "Too large resource version"
Summary: SDN pods failing to list due to "Too large resource version"
Keywords:
Status: CLOSED DUPLICATE of bug 1880341
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.5
Hardware: x86_64
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Jacob Tanenbaum
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-29 09:43 UTC by jnaess
Modified: 2020-11-03 14:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-03 14:25:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1879901 0 medium CLOSED [release 4.5] Top-level cross-platform: Fix bug in reflector not recovering from "Too large resource version" 2024-03-25 16:31:18 UTC

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 ***
Note You need to log in before you can comment on or make changes to this bug.