Bug 1596440
Summary: | OOMKilled build pod should surface that status on build object | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
Component: | Build | Assignee: | Ben Parees <bparees> |
Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10.0 | CC: | aos-bugs, erezende, wewang |
Target Milestone: | --- | ||
Target Release: | 3.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature: information about OOMKilled build pod gets propagated to a build object
Reason: it simplifies debugging and discovering what went awry if appropriate failure reasons are described to the user
Result: a build controller populates correctly the status reason and message when build pod is OOMKilled
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-11 07:20:43 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
Clayton Coleman
2018-06-29 01:35:37 UTC
Commits pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/a7acc5b46aeba921c9ee3b7dc6f631937340e5d9 Bug 1596440 - surface OOMKilled pod to build https://github.com/openshift/origin/commit/6b0c54066a9b718e16485e7a8f30a12035e9b015 Merge pull request #20297 from wozniakjan/bug-1596440/surface_oomkilled_in_build Bug 1596440 - surface OOMKilled pod to build *** Bug 1610437 has been marked as a duplicate of this bug. *** Verified in openshift v3.11.0-0.21.0 build already gave exactly error info about openshift killed the process because of OOM. steps: 1. create a project and set a low resource limit with follow info { "apiVersion": "v1", "kind": "LimitRange", "metadata": { "creationTimestamp": null, "name": "resource-limits" }, "spec": { "limits": [ { "type": "Pod", "max": { "cpu": "1", "memory": "100Mi" }, "min": { "cpu": "10m", "memory": "50Mi" } }, { "type": "Container", "default": { "cpu": "50m", "memory": "100Mi" }, "defaultRequest": { "cpu": "10m", "memory": "50Mi" } } ] } } 2. Check the info [root@qe-wewang-testmaster-etcd-1 ~]# oc describe limitrange -n wewang2 Name: resource-limits Namespace: wewang2 Type Resource Min Max Default Request Default Limit Max Limit/Request Ratio ---- -------- --- --- --------------- ------------- ----------------------- Pod memory 50Mi 100Mi - - - Pod cpu 10m 1 - - - Container cpu - - 10m 50m - Container memory - - 50Mi 100Mi - 3.Create apps in the limited project, check the build and build pod $ oc new-app nodejs-mongodb-example -n wewang2 $ oc get builds NAME TYPE FROM STATUS STARTED DURATION nodejs-mongodb-example-1 Source Git@b078bcf Failed (OutOfMemoryKilled) 6 minutes ago 1m26s $ oc get pods NAME READY STATUS RESTARTS AGE mongodb-1-deploy 1/1 Running 0 7m nodejs-mongodb-example-1-build 0/1 OOMKilled 0 7m 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652 |