Bug 2076831

Summary: [ocp4.11]Mem/cpu high utilization by apiserver/etcd for cluster stayed 10 hours
Product: OpenShift Container Platform Reporter: ge liu <geliu>
Component: EtcdAssignee: Allen Ray <alray>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.11CC: juzhao, mifiedle, qili, sreber, tjungblu, wking, xxia
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.11.0   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:07:44 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:
Bug Depends On:    
Bug Blocks: 2033575    

Comment 6 Xingxing Xia 2022-04-20 04:38:27 UTC
Increasing Severity because several QEs observed and reproduced this 4.11-cluster-dead issue after about 10 ~ 11 hours since fresh clusters were installed, see #forum-qe channel https://coreos.slack.com/archives/CH76YSYSC/p1650427961844569?thread_ts=1650379744.641499&cid=CH76YSYSC after I raised it for wider discussion and input.

Comment 20 Mike Fiedler 2022-04-20 13:29:41 UTC
Marking this as a TestBlocker since it prevents running a cluster > 12 hours

Comment 37 ge liu 2022-04-24 02:26:43 UTC
we have prepared cluster and waiting for its status after 12H

Comment 39 Qiujie Li 2022-04-25 01:41:18 UTC
A cluster with build 4.11.0-0.nightly-2022-04-22-182942 had been run for 2+ days. etcd memory usage increase reported in this bug was gone, cpu usage is normal. Attached  attachment 1874736 [details] .

Comment 41 errata-xmlrpc 2022-08-10 11:07:44 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.