Graph builder container of UpdateService instance is getting OOMKilled
Issue
- The
service
pods created by OpenShift Update Service operator are stuck incrashloobackoff
state.
$ oc get pods -n openshift-update-service
NAME READY STATUS RESTARTS AGE
service-xxxx 1/2 CrashLoopBackOff 8 2m
service-xxxx 1/2 CrashLoopBackOff 8 2m
updateservice-operator-xxxx 1/1 Running 0 2h
- The
graph-builder
container is getting constantly getting restarted due to invoking OOMKiller frequently.
lastState:
terminated:
containerID: cri-o://cbxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
exitCode: 137 <=============
finishedAt: '2021-08-16T05:08:32Z'
reason: OOMKilled <=============
startedAt: '2021-08-16T05:08:13Z'
name: graph-builder
Environment
- Red Hat OpenShift Container Platform
- 4.6+
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.