Bug 1377385

Summary: Check disk space on all mounted partitions used by OpenShift components
Product: OpenShift Container Platform Reporter: thunt
Component: RFEAssignee: Derek Carr <decarr>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aos-bugs, decarr, jokerman, mbarrett, mmccomas, pmorie
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: 2018-03-12 13:54: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:

Description thunt 2016-09-19 14:29:51 UTC
Description of problem:

Currently OpenShift only monitors disk space for the root partition and the Docker cache.
However for various reasons, separate partitions may be used for /var or /var/lib/origin and/or /var/lib/docker.

So OpenShift should either monitor disk space on all mounted partitions or for the directories that it specifically cares about.

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


How reproducible:
Very

Steps to Reproduce:
1. Move /var/lib/docker to separate partition
2. Disable any cap on docker log file size
3. Run elastic search with a bad NFS share configured as a persistent volume
4. .......

Actual results:


Expected results:


Additional info:

Comment 1 Andy Goldstein 2016-09-19 14:36:35 UTC
Note that this is really something that needs to be addressed upstream in Kubernetes and/or cadvisor.

Comment 2 Derek Carr 2016-09-30 13:17:17 UTC
Upstream discussion on this issue is here:
https://github.com/kubernetes/kubernetes/issues/30799

Comment 4 Eric Rich 2018-03-12 13:54:36 UTC
This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.