Description of problem: Containers which exceed their memory limit report their termination reason as Error, rather than OOMKilled. Version-Release number of selected component (if applicable): 4.4.0 How reproducible: Always Steps to Reproduce: 1. Create a pod with the following properties a. Low resource request and limits b. High actual memory usage 2. Run the pod Actual results: Pod terminates with reason Error Expected results: Pod should terminate with reason OOMKilled Additional info: This is blocking the kube 1.17 rebase in origin: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24286/pull-ci-openshift-origin-master-e2e-gcp-builds/790
Moving this to our active development branch (4.4.0) for Target.
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-2020:0581