Bug 1658385

Summary:	Container runtime should limit container storage
Product:	OpenShift Container Platform	Reporter:	brad.williams
Component:	Containers	Assignee:	Mrunal Patel <mpatel>
Status:	CLOSED DUPLICATE	QA Contact:	weiwei jiang <wjiang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-14 21:48:36 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 brad.williams 2018-12-11 22:44:15 UTC

Description of problem:

Observed on starter-ca-central-1 cluster. Our pre-upgrade diagnostics reported disk pressure on 10 compute nodes.  Upon further investigation, all 10 nodes had had their container storage fully consumed by a single rogue pod (tropospheric) that continuously creates a core dump on the container storage volume. 

Version-Release number of selected component (if applicable):

openshift v3.11.44
cri-o://1.11.9

How reproducible:
100%

Steps to Reproduce:
1. Create a project that continuously writes to the container storage volume.  

Actual results:

Eventually, this project will consume the entire disk and ultimately criple the container runtime.

Expected results:

Ideally, a container would not be able to consume all of the shared resources that the container runtime is providing.

Additional info:

Comment 1 Mrunal Patel 2019-01-14 21:48:36 UTC


*** This bug has been marked as a duplicate of bug 1658386 ***