Bug 1658385 - Container runtime should limit container storage
Summary: Container runtime should limit container storage
Keywords:
Status: CLOSED DUPLICATE of bug 1658386
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Mrunal Patel
QA Contact: weiwei jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-11 22:44 UTC by brad.williams
Modified: 2019-01-14 21:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-14 21:48:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.