Bug 1901677

Summary: apiserver 503 responses, timeouts, and throttling causing cluster to be slow or inaccessible
Product: OpenShift Container Platform Reporter: John Coleman <jocolema>
Component: openshift-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED CURRENTRELEASE QA Contact: Xingxing Xia <xxia>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, bshirren, jcrumple, jseunghw, mfojtik, openshift-bugs-escalate
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-05 10:27:42 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:

Comment 6 Stefan Schimanski 2020-11-26 10:12:25 UTC 
The messages about storage.InvalidError are noise coming from monitoring operator:

18144:2020-11-23T01:03:44.107376798Z E1123 01:03:44.107325       1 reflector.go:178] github.com/coreos/prometheus-operator/pkg/prometheus/operator.go:486: Failed to list *v1.PodMonitor: resourceVersion: Invalid value: "503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159": strconv.ParseUint: parsing "503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/503835159/^C

This is known and a fix is pending.
Comment 17 Stefan Schimanski 2021-02-05 10:27:42 UTC 
Closing following c16.
Comment 18 Red Hat Bugzilla 2023-09-15 00:51:54 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days